[apport] gnome-panel crashed with SIGSEGV in _int_malloc()

Bug #90383 reported by Bill Hand
2
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

I've been having a lot of trouble with gnome-panel as it gets closer to the release of Feisty. It seems to mostly occurr when I am working with the File Browser and moving things around a bit; I don't always get a crash report, but it has crashed several times here lately. I've noticed some changes to xorg files here lately... Not sure if tht is what is going on or not.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Mar 7 04:41:49 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 2.17.92-0ubuntu4
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-config-prefix /gnome-panel-Nyx8Dv/ --sm-client-id 117f000101000116622449200000048420001 --screen 0
ProcCwd: /home/crazyeccentric
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 _int_malloc () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 xmlStrndup () from /usr/lib/libxml2.so.2
 ?? () from /usr/lib/libxml2.so.2
 ?? ()
Uname: Linux CrazyEccentric 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio avahi-autoipd cdrom clamav dhcp dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Bill Hand (fxwgbill-gmail) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it? (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Bill Hand (fxwgbill-gmail) wrote : Re: [Bug 90383] Re: [apport] gnome-panel crashed with SIGSEGV in _int_malloc()

I will be more then happy to, however I'm not sure exactly how to go
about it... I assume I will need to 'kill' gnome-panel, which I can do
in the system monitor and then restart it with Valgrind? Won't killing
the gnome-panel make that hard to do? I'd like to know exactly how to
go about it, please, and what my indications will be. ( I do have
Valgrind installed and ready to go) I would think that I could set that
up in the startup script possibly too.... Please advise...

Thanx,

Bill

Sebastien Bacher wrote:
> Thanks for your bug report. The crash looks like a memory corruption.
> Could you try to get a valgrind log for it? (you can follow the
> instructions from https://wiki.ubuntu.com/Valgrind for that)
>
> ** Changed in: gnome-panel (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>
>

Revision history for this message
Bill Hand (fxwgbill-gmail) wrote :
Download full text (3.6 KiB)

Not sure if this helps or not... but there are errors.

crazyeccentric@CrazyEccentric:~$ valgrind gnome-panel
==29963== Memcheck, a memory error detector.
==29963== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==29963== Using LibVEX rev 1658, a library for dynamic binary translation.
==29963== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
==29963== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation
framework.
==29963== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.
==29963== For more details, rerun with: -v
==29963==
==29963== Syscall param writev(vector[...]) points to uninitialised byte(s)
==29963== at 0x4A85BED: do_writev (writev.c:46)
==29963== by 0x4F2D302: (within /usr/lib/libxcb.so.1.0.0)
==29963== by 0x4F2D89A: (within /usr/lib/libxcb.so.1.0.0)
==29963== by 0x4F2D9CC: (within /usr/lib/libxcb.so.1.0.0)
==29963== by 0x4F2DB1E: xcb_flush (in /usr/lib/libxcb.so.1.0.0)
==29963== by 0x48E8DDD: _XSend (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x48D692A: XQueryExtension (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x48CB6BA: XInitExtension (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x4B60DFF: XFixesFindDisplay (in
/usr/lib/libXfixes.so.3.1.0)
==29963== by 0x4B6109C: XFixesQueryExtension (in
/usr/lib/libXfixes.so.3.1.0)
==29963== by 0x45F2374: gdk_display_open (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==29963== by 0x45CFCBE: gdk_display_open_default_libgtk_only (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==29963== Address 0x515681C is 4,684 bytes inside a block of size 8,556
alloc'd
==29963== at 0x402095F: calloc (vg_replace_malloc.c:279)
==29963== by 0x4F2D510: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.0.0)
==29963== by 0x4F2FBF8: xcb_connect (in /usr/lib/libxcb.so.1.0.0)
==29963== by 0x48E7E9F: _XConnectXCB (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x48D0A28: XOpenDisplay (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x45F21C1: gdk_display_open (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==29963== by 0x45CFCBE: gdk_display_open_default_libgtk_only (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==29963== by 0x43A07A4: (within /usr/lib/libgtk-x11-2.0.so.0.1000.9)
==29963== by 0x4847F73: g_option_context_parse (in
/usr/lib/libglib-2.0.so.0.1200.11)
==29963== by 0x415FE88: gnome_program_parse_args (in
/usr/lib/libgnome-2.so.0.1786.6)
==29963== by 0x41611DC: (within /usr/lib/libgnome-2.so.0.1786.6)
==29963== by 0x4161510: gnome_program_init (in
/usr/lib/libgnome-2.so.0.1786.6)
==29963==
==29963== ERROR SUMMARY: 9 errors from 1 contexts (suppressed: 185 from 2)
==29963== malloc/free: in use at exit: 1,850,598 bytes in 20,108 blocks.
==29963== malloc/free: 131,318 allocs, 111,210 frees, 23,572,473 bytes
allocated.
==29963== For counts of detected errors, rerun with: -v
==29963== searching for pointers to 20,108 not-freed blocks.
==29963== checked 2,484,632 bytes.
==29963==
==29963== LEAK SUMMARY:
==29963== definitely lost: 38,454 bytes in 1,367 blocks.
==29963== possibly lost: 98,200 bytes in 138 blocks.
==29963== still reachable: 1,713,944 bytes in 18,603 blocks.
==29963== suppressed: 0 bytes in 0 blo...

Read more...

Revision history for this message
Bill Hand (fxwgbill-gmail) wrote :

I am also getting Nautilus crashes, but it doesn't come up in the Bug
Reporting proggy... Below is what comes up in a box:

"Nautilus can't be used now, due to an unexpected error."

"Nautilus can't be used now, due to an unexpected error from Bonobo when
attempting to locate the factory.Killing bonobo-activation-server and
restarting Nautilus may help fix the problem."

When this crash occurred, what I was doing was looking through some
things I had downloaded with Azureus and was going to copy them and put
them in the directory I use for ebooks. All the sudden the file manager
closed and up pops the error on my other monitor. I run dual 19" flat
panel monitors and have it set up as if I have two totally separate
puters, (two sep desktops). It doesn't seem to matter which monitor I
am working with File Manager on, it does it on both 'sides'

If you need any further info or I can help in any way, please let me
know....

Bill

Sebastien Bacher wrote:
> Thanks for your bug report. The crash looks like a memory corruption.
> Could you try to get a valgrind log for it? (you can follow the
> instructions from https://wiki.ubuntu.com/Valgrind for that)
>
> ** Changed in: gnome-panel (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for the work on that. the valgrind log is not useful. You can use "gnome-session-remove gnome-panel" then run valgrind

Revision history for this message
Bill Hand (fxwgbill-gmail) wrote :
Download full text (5.0 KiB)

OK... this is what I get when I first start valgrind... I see errors
but not sure if it's what you need. I assume you want me to leave it
running for a while and see what all happens when the panel crashes...
It's already at when I click on the 'frame' of the 'windows' to move a
window to a diff desktop, it cycles and won't let me do it. Only way I
can move things is minimize them down to the taskbar and then I can
right click and move the item to a diff desktop. I think I am explaining
that right....

do you want me to turn on any of the swithces?

Here is from the first 5 mins of running valgrind:

crazyeccentric@CrazyEccentric:~$ sudo gnome-session-remove gnome-panel
Password:
Removing 'gnome-panel' from the session
crazyeccentric@CrazyEccentric:~$ sudo valgrind gnome-panel
==11417== Memcheck, a memory error detector.
==11417== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==11417== Using LibVEX rev 1658, a library for dynamic binary translation.
==11417== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
==11417== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation
framework.
==11417== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.
==11417== For more details, rerun with: -v
==11417==
==11417== Syscall param writev(vector[...]) points to uninitialised byte(s)
==11417== at 0x4AAEBED: do_writev (writev.c:46)
==11417== by 0x4F2D302: (within /usr/lib/libxcb.so.1.0.0)
==11417== by 0x4F2D89A: (within /usr/lib/libxcb.so.1.0.0)
==11417== by 0x4F2D9CC: (within /usr/lib/libxcb.so.1.0.0)
==11417== by 0x4F2DB1E: xcb_flush (in /usr/lib/libxcb.so.1.0.0)
==11417== by 0x4911DDD: _XSend (in /usr/lib/libX11.so.6.2.0)
==11417== by 0x48FF92A: XQueryExtension (in /usr/lib/libX11.so.6.2.0)
==11417== by 0x48F46BA: XInitExtension (in /usr/lib/libX11.so.6.2.0)
==11417== by 0x4B89DFF: XFixesFindDisplay (in
/usr/lib/libXfixes.so.3.1.0)
==11417== by 0x4B8A09C: XFixesQueryExtension (in
/usr/lib/libXfixes.so.3.1.0)
==11417== by 0x461B374: gdk_display_open (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==11417== by 0x45F8CBE: gdk_display_open_default_libgtk_only (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==11417== Address 0x51567FC is 4,684 bytes inside a block of size 8,556
alloc'd
==11417== at 0x402095F: calloc (vg_replace_malloc.c:279)
==11417== by 0x4F2D510: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.0.0)
==11417== by 0x4F2FBF8: xcb_connect (in /usr/lib/libxcb.so.1.0.0)
==11417== by 0x4910E9F: _XConnectXCB (in /usr/lib/libX11.so.6.2.0)
==11417== by 0x48F9A28: XOpenDisplay (in /usr/lib/libX11.so.6.2.0)
==11417== by 0x461B1C1: gdk_display_open (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==11417== by 0x45F8CBE: gdk_display_open_default_libgtk_only (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==11417== by 0x43C97A4: (within /usr/lib/libgtk-x11-2.0.so.0.1000.9)
==11417== by 0x4870F73: g_option_context_parse (in
/usr/lib/libglib-2.0.so.0.1200.11)
==11417== by 0x4188E88: gnome_program_parse_args (in
/usr/lib/libgnome-2.so.0.1786.6)
==11417== by 0x418A1DC: (within /usr/lib/libgnome-2.so.0.1786.6)
==11417== by 0x418A510: gnome_program_init (in
...

Read more...

Revision history for this message
Bill Hand (fxwgbill-gmail) wrote :
Download full text (90.5 KiB)

OK... this is valgrind with everything that I typically have running:

crazyeccentric@CrazyEccentric:~$ gnome-session-remove gnome-panel
Removing 'gnome-panel' from the session
crazyeccentric@CrazyEccentric:~$ valgrind gnome-panel
==12016== Memcheck, a memory error detector.
==12016== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==12016== Using LibVEX rev 1658, a library for dynamic binary translation.
==12016== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
==12016== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation
framework.
==12016== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.
==12016== For more details, rerun with: -v
==12016==
==12016== Syscall param writev(vector[...]) points to uninitialised byte(s)
==12016== at 0x4A85BED: do_writev (writev.c:46)
==12016== by 0x4F2D302: (within /usr/lib/libxcb.so.1.0.0)
==12016== by 0x4F2D89A: (within /usr/lib/libxcb.so.1.0.0)
==12016== by 0x4F2D9CC: (within /usr/lib/libxcb.so.1.0.0)
==12016== by 0x4F2DB1E: xcb_flush (in /usr/lib/libxcb.so.1.0.0)
==12016== by 0x48E8DDD: _XSend (in /usr/lib/libX11.so.6.2.0)
==12016== by 0x48D692A: XQueryExtension (in /usr/lib/libX11.so.6.2.0)
==12016== by 0x48CB6BA: XInitExtension (in /usr/lib/libX11.so.6.2.0)
==12016== by 0x4B60DFF: XFixesFindDisplay (in
/usr/lib/libXfixes.so.3.1.0)
==12016== by 0x4B6109C: XFixesQueryExtension (in
/usr/lib/libXfixes.so.3.1.0)
==12016== by 0x45F2374: gdk_display_open (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==12016== by 0x45CFCBE: gdk_display_open_default_libgtk_only (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==12016== Address 0x515681C is 4,684 bytes inside a block of size 8,556
alloc'd
==12016== at 0x402095F: calloc (vg_replace_malloc.c:279)
==12016== by 0x4F2D510: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.0.0)
==12016== by 0x4F2FBF8: xcb_connect (in /usr/lib/libxcb.so.1.0.0)
==12016== by 0x48E7E9F: _XConnectXCB (in /usr/lib/libX11.so.6.2.0)
==12016== by 0x48D0A28: XOpenDisplay (in /usr/lib/libX11.so.6.2.0)
==12016== by 0x45F21C1: gdk_display_open (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==12016== by 0x45CFCBE: gdk_display_open_default_libgtk_only (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==12016== by 0x43A07A4: (within /usr/lib/libgtk-x11-2.0.so.0.1000.9)
==12016== by 0x4847F73: g_option_context_parse (in
/usr/lib/libglib-2.0.so.0.1200.11)
==12016== by 0x415FE88: gnome_program_parse_args (in
/usr/lib/libgnome-2.so.0.1786.6)
==12016== by 0x41611DC: (within /usr/lib/libgnome-2.so.0.1786.6)
==12016== by 0x4161510: gnome_program_init (in
/usr/lib/libgnome-2.so.0.1786.6)

(gnome-panel:12016): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
to allocate widget with width -15 and height 25

(gnome-panel:12016): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
to allocate widget with width -15 and height 25
==12016==
==12016== Syscall param writev(vector[...]) points to uninitialised byte(s)
==12016== at 0x4A85BED: do_writev (writev.c:46)
==12016== by 0x4F2D302: (within /usr/lib/libxcb.so.1.0.0)
==12016== by 0x4F2D89A: (within /usr/lib/libxcb.so.1.0.0)
==12016== by 0x4F2E0AF: xc...

Revision history for this message
Bill Hand (fxwgbill-gmail) wrote :

Something else that has just happened; I believe there were some Gnome
updates in the last couple days; after a reboot earlier this evening,
nothing 'docks' in the system tray anymore. I can look in the system
monitor and it's in there that 'it' is loaded up, but nothing in the
system tray. That second log that I sent in, is with the docking
problem...

Sebastien Bacher wrote:
> thank you for the work on that. the valgrind log is not useful. You can
> use "gnome-session-remove gnome-panel" then run valgrind
>
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your work, those valgrind logs have no error though

Revision history for this message
Bill Hand (fxwgbill-gmail) wrote :

Ok... I didn't know if maybe you could see something that was not
right. I have valgrind running and will let it run until something
'breaks'. I assume that the errors in there are normal...

Bill

Sebastien Bacher wrote:
> Thank you for your work, those valgrind logs have no error though
>
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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