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 578520 - Crash in load_graph_change_speed at load-graph.cpp line 736
Crash in load_graph_change_speed at load-graph.cpp line 736
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: general
2.28.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 631208 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-09 18:28 UTC by Chris Coulson
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28

Attachments
patch to remove unnecessary assert (696 bytes, patch)
2011-11-04 20:17 UTC, Robert Roth 		none Details | Review

Description Chris Coulson 2009-04-09 18:28:13 UTC 
Steps to reproduce:
This was reported at https://bugs.edge.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/358387:

"I open gnome-system-monitor, I go to Edit -> Preferences and I change, in the tabs, the time intervals. Then, gnome-system-monitor crashes."

Stack trace:
ERROR:load-graph.cpp:736:void load_graph_change_speed(LoadGraph*, guint): assertion failed: (g->timer_index)

Program received signal SIGABRT, Aborted.

+ Trace 214326

Thread 3063854928 (LWP 5080)

  • #0 __kernel_vsyscall
  • #1 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #2 *__GI_abort
    at abort.c line 88
  • #3 IA__g_assertion_message
  • #4 IA__g_assertion_message_expr
  • #5 load_graph_change_speed
    at load-graph.cpp line 736
  • #6 timeouts_changed_cb
    at procman.cpp line 152
  • #7 notify_listeners_callback
    at gconf-client.c line 2385
  • #8 gconf_listeners_notify
    at gconf-listeners.c line 590
  • #9 notify_one_entry
    at gconf-client.c line 2410
  • #10 notify_idle_callback
    at gconf-client.c line 2450
  • #11 g_idle_dispatch
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c line 3922
  • #12 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c line 1814
  • #13 g_main_context_iterate
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c line 2448
  • #14 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.20.0/glib/gmain.c line 2656
  • #15 IA__gtk_main
    at /build/buildd/gtk+2.0-2.16.0/gtk/gtkmain.c line 1205
  • #16 Gtk::Main::run_impl
    at main.cc line 536
  • #17 Gtk::Main::run
    at main.cc line 483
  • #18 main
    at procman.cpp line 742 


Other information:
Comment 1 Adam Dingle 2010-03-03 20:27:03 UTC 
I see this crash too.  I'm using System Monitor 2.28.0 on Ubuntu 9.10.
Comment 2 what else 2010-09-18 17:29:45 UTC 
This bug has been submitted on 2009-04-09 and there is still no progress or what so ever. The developer needs some slapping in the face or this bug will stay for years!

In Maverick the same is still the case and crashes with error:
ERROR:load-graph.cpp:742:void load_graph_change_speed(LoadGraph*, guint): assertion failed: (g->timer_index)
ptrace: Operation not permitted.
/home/ezflow/2966: No such file or directory.
No stack.

If i run system monitor with sudo it does not crash so something is up with the permissions.
Comment 3 Akhil Laddha 2010-10-03 14:05:39 UTC 
*** Bug 631208 has been marked as a duplicate of this bug. ***
Comment 4 Akhil Laddha 2010-10-03 14:06:56 UTC 
last dupe in 2.28.x
Comment 5 Thibault Lemaitre 2011-02-14 09:38:43 UTC 
Hello,

I also have this bug on Ubuntu 10.10 (upgraded from an Ubuntu 10.04) and gnome-system-monitor 2.28.1, with the following error :

ERROR:load-graph.cpp:742:void load_graph_change_speed(LoadGraph*, guint): assertion failed: (g->timer_index)

Note the difference with the first comment : 736 vs 742.

For me, this problem occurs only when I change the refreshing frequency in the  resources preferences tab's.
In the preferences window's, if I change the value in the other tabs (processes and file system), everything is ok. From the moment I change the value in the resources tab's, the next click (on close or another tab or the case to tick), gnome-system crash with the error previously mentioned.

As a workaround : if I selected the resources tab before to go in the preferences, I was able to change the refreshing frequency fro the resources without crash. Then I could select the tab I wanted before to open the preferences and change the value without crash

(my English is may be not so easy to well understand, cause I'm French, just tell me if it's not well understandable!)
Comment 6 Chris Kühl 2011-02-23 23:25:03 UTC 
I'm getting this but only occasionally. I also only get this with the resources tab. I'll try to track it down.
Comment 7 Robert Roth 2011-11-04 20:17:08 UTC 
Created attachment 200714 [details] [review]
patch to remove unnecessary assert

I can reproduce it all the time, by changing the refresh frequency on the Resources tab, and selecting another tab. I always get the ERROR:load-graph.cpp:xxx:void load_graph_change_speed(LoadGraph*, guint):
assertion failed: (g->timer_index) message. Checking the code, there is an assert to make sure the pointer is not a nullpointer, and after that it's also checked with an if statement, so removing the assert will not cause the crash anymore, and will not cause any harm.
Comment 8 Chris Kühl 2011-11-04 23:57:06 UTC 
Fixed in commit dbc19ed7fa89ddd426028a45265ea49857272637

Thanks.