gnome-system-monitor assert failure: ERROR:../src/load-graph.cpp:557:void net_scale(LoadGraph*, guint64, guint64): assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10))))

Bug #1878607 reported by Marc Poirette
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

1) Ubuntu 20.04 LTS / Raspberry 4b
2) gnome-system-monitor:
  Installé : 3.36.0-1
  Candidat : 3.36.0-1
 Table de version :
 *** 3.36.0-1 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages
        100 /var/lib/dpkg/status
3) -
4) gnome-system-monitor crashes with:
ERROR:../src/load-graph.cpp:557:void net_scale(LoadGraph*, guint64, guint64): assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10))))
Bail out! ERROR:../src/load-graph.cpp:557:void net_scale(LoadGraph*, guint64, guint64): assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10))))
Abandon (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-system-monitor 3.36.0-1
ProcVersionSignature: User Name 5.4.0-1008.8-raspi 5.4.29
Uname: Linux 5.4.0-1008-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27
Architecture: arm64
AssertionMessage: ERROR:../src/load-graph.cpp:557:void net_scale(LoadGraph*, guint64, guint64): assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10))))
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Flashback:GNOME
Date: Thu May 14 14:36:52 2020
ExecutablePath: /usr/bin/gnome-system-monitor
ProcCmdline: gnome-system-monitor
Signal: 6
SourcePackage: gnome-system-monitor
Title: gnome-system-monitor assert failure: ERROR:../src/load-graph.cpp:557:void net_scale(LoadGraph*, guint64, guint64): assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10))))
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2020-05-08T18:00:39.352301
separator:

Revision history for this message
Marc Poirette (marc-p-59) wrote :
Revision history for this message
Marc Poirette (marc-p-59) wrote :
Download full text (10.0 KiB)

ubuntu@ubuntu:~$ apport-retrace --stdout /var/crash/_usr_bin_gnome-system-monitor.1000.crash
dpkg-source: info: extraction de gnome-system-monitor dans gnome-system-monitor-3.36.0
dpkg-source: info: extraction de gnome-system-monitor_3.36.0.orig.tar.xz
dpkg-source: info: extraction de gnome-system-monitor_3.36.0-1.debian.tar.xz
--- stack trace ---
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
        set = {__val = {0, 281473323341584, 2048, 281473372209152, 1, 281474745384656, 281473371215320, 281474745384848, 281473371219612, 281473372199520, 2048, 281473323341584, 281473323342176, 281474745384864, 281473370856720, 187651656678736}}
        pid = <optimized out>
        tid = <optimized out>
        ret = <optimized out>
#1 0x0000ffffa0489d68 in __GI_abort () at abort.c:79
        save_stage = 1
        act = {__sigaction_handler = {sa_handler = 0xfffff2364100, sa_sigaction = 0xfffff2364100}, sa_mask = {__val = {281473403490656, 187651656678736, 281473404272088, 281473404272384, 161, 187650629309544, 281474745385288, 18446744073709551615, 18446744073709551615, 18446744073709551615, 187651659148496, 281474745385216, 281473403490628, 281474745385216, 281473403490656, 187651656678736}}, sa_flags = 161, sa_restorer = 0xaaaad11a1468}
        sigs = {__val = {32, 0 <repeats 15 times>}}
#2 0x0000ffffa23a9174 in g_assertion_message (domain=domain@entry=0x0, file=file@entry=0xaaaad11a1468 "../src/load-graph.cpp", line=line@entry=557, func=func@entry=0xaaaad11a14c0 "void net_scale(LoadGraph*, guint64, guint64)", message=message@entry=0xaaab0e16f280 "assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10))))") at ../../../glib/gtestutils.c:2914
        lstr = "557\000\000\000\000\000\200\024\032Ѫ\252\000\000\270\237k\240\377\377\000\000@\000\000\000\000\000\000"
        s = 0xaaab0e567d50 "0 \212\016\253\252"
#3 0x0000ffffa23a91d8 in g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0xaaaad11a1468 "../src/load-graph.cpp", line=line@entry=557, func=func@entry=0xaaaad11a14c0 "void net_scale(LoadGraph*, guint64, guint64)", expr=expr@entry=0xaaaad11a1480 "new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10)))") at ../../../glib/gtestutils.c:2940
        s = 0xaaab0e16f280 "assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10))))"
#4 0x0000aaaad118acb8 in net_scale (dout=18446744073709551615, din=18446744073709551615, graph=0xaaab0e7bacd0) at ../src/load-graph.cpp:557
        pow2 = <optimized out>
        base10 = <optimized out>
        coef10 = <optimized out>
        factor10 = <optimized out>
        dmax = <optimized out>
        new_max = 18446744073709551615
        bak_max = 18446744073709551615
        scale = <optimized out>
        dmax = <optimized out>
        new_max = <optimized out>
        bak_max = <optimized out>
        __func__ = <optimized out>
        __PRETTY_FUNCTION__ = <optimized out>
        scale = <optimized out>
        ticks = <optimized out>
        bit_max = <optimized out>
        d = <optimized out>
        pow2 = <optimized out>
        base10 = <optimized out>
        coef10 = <optimized out>
        factor10 = <...

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x0000ffffa049d070 in ?? ()
 #1 0x0000fffff2363e98 in ?? ()
 #2 0x0000ffffa04e0c38 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-arm64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, the reports seem to be from armhf, could someone having the hardware and issue report it upstream to
https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues

information type: Private → Public
Changed in gnome-system-monitor (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.