baobab crashed with SIGSEGV in g_slice_alloc()

[Paul Hannah]

Binary package hint: gnome-utils

was scanning, died.

ProblemType: Crash
Architecture: i386
Date: Fri Jul 13 18:21:09 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/baobab
NonfreeKernelModules: vmnet vmblock vmmon
Package: gnome-utils 2.18.1-1ubuntu1
PackageArchitecture: i386
ProcCmdline: baobab
ProcCwd: /home/pkh
ProcEnviron:
 PATH=/home/pkh/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-utils
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 gdk_region_rectangle () from /usr/lib/libgdk-x11-2.0.so.0
 gdk_window_invalidate_maybe_recurse ()
 gdk_window_invalidate_maybe_recurse ()
 gdk_window_invalidate_region ()
Title: baobab crashed with SIGSEGV in g_slice_alloc()
Uname: Linux D610 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__gdk_region_rectangle (rectangle=0xbf9e9ff0) at /build/buildd/gtk+2.0-2.11.5/gdk/gdkregion-generic.c:143
IA__gdk_window_invalidate_maybe_recurse (window=0x8088a18, region=0x85a7940, child_func=0xb76cdd70 <true_predicate>, user_data=0x0)
IA__gdk_window_invalidate_maybe_recurse (window=0x8088508, region=0x85a79c0, child_func=0xb76cdd70 <true_predicate>, user_data=0x0)
IA__gdk_window_invalidate_region (window=0x8088508, region=0x85a79c0, invalidate_children=1) at /build/buildd/gtk+2.0-2.11.5/gdk/gdkwindow.c:2712
IA__gdk_window_invalidate_rect (window=0x8088508, rect=0xbf9ea0dc, invalidate_children=1) at /build/buildd/gtk+2.0-2.11.5/gdk/gdkwindow.c:2530

[Sebastien Bacher (seb128)]

Thanks for your bug report. Could you try to get a valgrind log for the crash (you can follow the instructions on https://wiki.ubuntu.com/Valgrind)?

[Paul Hannah (pkhannah)]

Sorry, it's never happened again, so I don't think I could recreate it...

If I see it again and think I can recreate it I'll run it through
valgrind and update the bug.

Sebastien Bacher wrote:
> Thanks for your bug report. Could you try to get a valgrind log for the
> crash (you can follow the instructions on
> https://wiki.ubuntu.com/Valgrind)?
>
> ** Changed in: gnome-utils (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: New => Incomplete
>

[Sebastien Bacher (seb128)]

closing for now then, feel free to reopen if you get the bug again

[Arun (arunmarjun)]

This happened to me today. I was running it and I had a subfolder mounted through sshfs. Am not sure if that was the issue. It crashed once even after I disabled scanning that filesystem

[Sebastien Bacher (seb128)]

don't reopen closed bugs only because you have a similar issue, you should rather open a new bug