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 384870 - crash in Disk Usage Analyzer: Analyzing the disk
crash in Disk Usage Analyzer: Analyzing the disk
Status: RESOLVED OBSOLETE
Product: gnome-utils
Classification: Deprecated
Component: baobab
2.16.x
Other All
: High critical
: ---
Assigned To: Fabio Marzocca
gnome-utils Maintainers
: 425634 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-11 22:58 UTC by mzanfardino
Modified: 2010-12-30 09:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mzanfardino 2006-12-11 22:58:36 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Analyzing the disk


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 109506560 vsize: 0 resident: 109506560 share: 0 rss: 70787072 rss_rlim: 0
CPU usage: start_time: 1165877212 rtime: 0 utime: 5193 stime: 0 cutime:1738 cstime: 0 timeout: 3455 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/baobab'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225238864 (LWP 32145)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 93399

Thread 1 (Thread -1225238864 (LWP 32145))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_slice_alloc
    from /usr/lib/libglib-2.0.so.0
  • #5 IA__gdk_region_rectangle
    at gdkregion-generic.c line 143
  • #6 IA__gtk_widget_region_intersect
    at gtkwidget.c line 4174
  • #7 IA__gtk_container_propagate_expose
    at gtkcontainer.c line 2457
  • #8 gtk_container_expose_child
    at gtkcontainer.c line 2349
  • #9 gtk_box_forall
    at gtkbox.c line 670
  • #10 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #11 gtk_container_expose
    at gtkcontainer.c line 2372
  • #12 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #13 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #19 IA__gtk_container_propagate_expose
    at gtkcontainer.c line 2461
  • #20 gtk_container_expose_child
    at gtkcontainer.c line 2349
  • #21 gtk_bin_forall
    at gtkbin.c line 133
  • #22 IA__gtk_container_forall
    at gtkcontainer.c line 1261
  • #23 gtk_container_expose
    at gtkcontainer.c line 2372
  • #24 gtk_window_expose
    at gtkwindow.c line 6070
  • #25 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #26 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #31 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #32 IA__gtk_main_do_event
    at gtkmain.c line 1403
  • #33 gdk_window_process_updates_internal
    at gdkwindow.c line 2324
  • #34 IA__gdk_window_process_updates
    at gdkwindow.c line 2431
  • #35 animation_timeout
    at gtkimage.c line 1376
  • #36 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #37 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #38 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #39 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #40 IA__gtk_main_iteration
    at gtkmain.c line 1107
  • #41 fill_model
  • #42 baobab_hardlinks_array_add
  • #43 baobab_hardlinks_array_add
  • #44 baobab_hardlinks_array_add
  • #45 baobab_hardlinks_array_add
  • #46 getDir
  • #47 start_proc_on_dir
  • #48 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #49 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #50 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #51 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #52 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #53 IA__gtk_widget_activate
    at gtkwidget.c line 3942
  • #54 IA__gtk_menu_shell_activate_item
    at gtkmenushell.c line 1024
  • #55 gtk_menu_shell_button_release
    at gtkmenushell.c line 630
  • #56 gtk_menu_button_release
    at gtkmenu.c line 2619
  • #57 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #58 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #59 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #60 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #61 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #62 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #63 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #64 IA__gtk_propagate_event
    at gtkmain.c line 2211
  • #65 IA__gtk_main_do_event
    at gtkmain.c line 1445
  • #66 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #67 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #68 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #69 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #70 IA__gtk_main
    at gtkmain.c line 1024
  • #71 main
  • #0 __kernel_vsyscall 






Comment 1


Marc-Andre Lureau





          2007-02-08 17:03:26 UTC
        



Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

This looks like a memory corruption pb.







Comment 2


palfrey





          2007-04-08 20:01:03 UTC
        



*** Bug 425634 has been marked as a duplicate of this bug. ***






Comment 3


Pedro Villavicencio





          2007-11-13 18:35:41 UTC
        



Re opening due to a dup on Ubuntu, I'm asking for a valgrind log there. 

https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/149977






Comment 4


Teppo Turtiainen





          2007-12-08 07:44:01 UTC
        



A decent stack trace. Confirming.






Comment 5


Akhil Laddha





          2010-12-30 09:46:26 UTC
        



Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.