After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 549383 - network assertion in the resource tab
network assertion in the resource tab
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: resources
2.22.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-26 02:35 UTC by Paul Rawson
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Paul Rawson 2008-08-26 02:35:00 UTC
Version: 2.22.3

What were you doing when the application crashed?
Switching wireless networks with NetworkManager


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.22.3 2008-08-11 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-gentoo-r7 #2 SMP PREEMPT Sat Jul 26 16:57:11 PDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 42450944 vsize: 42450944 resident: 16150528 share: 13172736 rss: 16150528 rss_rlim: 4294967295
CPU usage: start_time: 1219718030 rtime: 51 utime: 45 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-system-monitor'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb7f656d0 (LWP 26167)]
0xb7fa5424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb7f656d0 (LWP 26167))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374


----------- .xsession-errors (463440 sec old) ---------------------
	->lsb/usr/HP/hp-psc_2150_series-hpijs.ppd.gz (HP PSC 2150 series Foomatic/hpijs, hpijs 2.8.6.20b[0]) and
	->foomatic-ppds/HP/hp-psc_2150_series-hpijs.ppd.gz (HP PSC 2150 series Foomatic/hpijs, hpijs 2.8.6.20b)[0]

** (gnome-cups-add:1052): WARNING **: Two ppds have driver == 'hpijs, hpijs 2.8.6.20b'
	->lsb/usr/HP/hp-psc_2170_series-hpijs.ppd.gz (HP PSC 2170 series Foomatic/hpijs, hpijs 2.8.6.20b[0]) and
	->foomatic-ppds/HP/hp-psc_2170_series-hpijs.ppd.gz (HP PSC 2170 series Foomatic/hpijs, hpijs 2.8.6.20b)[0]

** (gnome-cups-add:1052): WARNING **: Two ppds have driver == 'hpijs, hpijs 2.8.6.20b'
	->lsb/usr/HP/hp-psc_2200_series-hpijs.ppd.gz (HP PSC 2200 series Foomatic/hpijs, hpijs 2.8.6.20b[0]) and
	->foomatic-ppds/HP/hp-psc_2200_series-hpijs.ppd.gz (HP PSC 2200 series Foomatic/hpijs, hpijs 2.8.6.20b)[0]

** (gnome-cups-add:1052): WARNING **: Two ppds have driver == 'hpijs, hpijs 2.8.6.20b'
	->lsb/usr/HP/hp-psc_2210_series-hpijs.ppd.gz (HP PSC 2210 series Foomatic/hpijs, hpijs 2.8.6.20b[0]) and
	->foomatic-ppds/HP/hp-psc_2210_series-hpijs.ppd.gz (HP PSC
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Paul Rawson 2008-08-26 02:37:49 UTC
This bug is reproducible. It occurs the moment NetworkManager's notification popup says You are now connected to the wireless network.
Comment 2 Benoît Dejean 2008-08-26 08:42:02 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

That stacktrace looks weird, net_scale (g=0x888c800, din=692622044, dout=166773341), din/dout are unrealistic.

Now i think about it, if it's reproducible, could you please start gnome-system-monitor from a terminal like this:

GNOME_SYSTEM_MONITOR_DEBUG= gnome-system-monitor

that should spit some debug info.

Comment 3 Paul Rawson 2008-08-31 08:48:43 UTC
Sorry it took so long to get the info -- the bug quit happening for a little while. Anyway, here it is:

** (gnome-system-monitor:27039): DEBUG: [22.909 load-graph.cpp:418 net_scale] bak 1400202648 new_max 314572800 pow2 27 coef10 300
**
** ERROR:(load-graph.cpp:419):void net_scale(LoadGraph*, unsigned int, unsigned int): assertion failed: (bak_max <= new_max)
Could not find the frame base for "IA__g_spawn_command_line_sync".
Could not find the frame base for "IA__g_assertion_message".
Could not find the frame base for "IA__g_assertion_message_expr".
Could not find the frame base for "g_timeout_dispatch".
Could not find the frame base for "g_main_context_iterate".
Could not find the frame base for "Gtk::Main::run_impl()".
Could not find the frame base for "IA__g_spawn_sync".

And just in case something else caused it this time, (it was while switching networks again) here's what bug buddy spits out:

Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.22.3 2008-08-11 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-gentoo-r7 #3 SMP PREEMPT Sun Aug 24 02:12:30 PDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 42450944 vsize: 42450944 resident: 16080896 share: 13103104 rss: 16080896 rss_rlim: 4294967295
CPU usage: start_time: 1220172257 rtime: 134 utime: 126 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-system-monitor'

[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb80056d0 (LWP 27039)]
0xb8045424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb80056d0 (LWP 27039))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374


----------- .xsession-errors (203004 sec old) ---------------------
 channel=java.nio.channels.SocketChannel[closed], socket=Socket[unconnected], local_address=0.0.0.0/0.0.0.0, local_port=0, remote_address=<null>, remote_port=0
    TCPConnectionManager::mainLoop::-1,TCPConnectionManager::access$900::-1,TCPConnectionManager$5::runSupport::-1,AEThread::run::-1
java.net.SocketException: Network is unreachable
	at sun.nio.ch.Net.connect(Native Method)
	at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.addNewRequest(Unknown Source)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.addNewOutboundRequests(Unknown Source)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.mainLoop(Unknown Source)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.access$900(Unknown Source)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager$5.runSupport(Unknown Source)
	at org.gudy.azureus2.core3.util.AEThread.run(Unknown Source)
DEBUG::Thu Aug 28 17:21:18 PDT 2008::com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager::addNewOutboundRequests::-1:
  ConnectDisconnectManager::address exception: full=/2001:0:d5c7:a2ca:0:ef7c:ab22:590:56949, hostname=2001:0:d5c7:a2ca:0:ef7c:ab22:590, port=56949, unresolved=false, full_sub=2001:0:d5c7:a2ca:0:ef7c:a
 channel=java.nio.channels.SocketChannel[closed], socket=Socket[unconnected], local_addr
...Too much output, ignoring rest...
--------------------------------------------------
Comment 4 Benoît Dejean 2008-08-31 10:35:57 UTC
Ok, the valuable info are:

** (gnome-system-monitor:27039): DEBUG: [22.909 load-graph.cpp:418 net_scale]
bak 1400202648 new_max 314572800 pow2 27 coef10 300

  • #14 net_scale
    at load-graph.cpp line 419

Thanks a lot !


I'm a bit surprised because interface that are down are always acounted to avoid spikes and this kind of overflow. But in this case, it definitely looks like: sunddenly, one interface appears with none-zero stats (din=1050972945, dout=1400202648) which makes the little math crazy, it then overflows, wraps around and triggers the assertion.
Comment 5 Benoît Dejean 2008-09-06 07:28:10 UTC
Fixed in 2.23.91 + 2.22.4.
Thanks.