metacity crashed with SIGSEGV in free()

Bug #157627 reported by miked
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: metacity

/usr/share/apport/apport-gtk

ProblemType: Crash
Architecture: i386
Date: Sat Oct 13 08:57:28 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/metacity
NonfreeKernelModules: cdrom
Package: metacity 1:2.20.0-0ubuntu3
PackageArchitecture: i386
ProcCmdline: /usr/bin/metacity --sm-client-id=default0
ProcCwd: /root
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: metacity
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 IA__g_free (mem=0x834ee00) at /build/buildd/glib2.0-2.14.1/glib/gmem.c:187
 IA__g_slist_foreach (list=0x8339840, func=0x8050a24 <g_free@plt>, user_data=0x0) at /build/buildd/glib2.0-2.14.1/glib/gslist.c:468
 meta_free_gslist_and_elements (list_to_deep_free=0x8339840) at util.c:205
 meta_window_free (window=0x834e728, timestamp=2585106946) at window.c:1000
Title: metacity crashed with SIGSEGV in free()
Uname: Linux Ubuntu710GustyGibbonBeta 2.6.22-14-rt #1 SMP PREEMPT RT Mon Oct 15 01:05:51 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse plugdev scanner tape

Tags: apport-crash
Revision history for this message
miked (miked11) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:free () from /lib/tls/i686/cmov/libc.so.6
IA__g_free (mem=0x834ee00) at /build/buildd/glib2.0-2.14.1/glib/gmem.c:187
IA__g_slist_foreach (list=0x8339840, func=0x8050a24 <g_free@plt>, user_data=0x0) at /build/buildd/glib2.0-2.14.1/glib/gslist.c:468
meta_free_gslist_and_elements (list_to_deep_free=0x8339840) at util.c:205
meta_window_free (window=0x834e728, timestamp=2585106946) at window.c:1000

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in metacity:
importance: Undecided → Medium
Revision history for this message
miked (miked11) wrote :

changed from private to public

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in metacity:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Marnanel Thurman (marnanel) wrote :

Is this repeatable?

Revision history for this message
miked (miked11) wrote :

root@Ubuntu710GustyGibbonBeta:~# sudo apt-get install valgrind
Reading package lists... Done
Building dependency tree
Reading state information... Done
valgrind is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@Ubuntu710GustyGibbonBeta:~# G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log metacity
Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager.
root@Ubuntu710GustyGibbonBeta:~#

Revision history for this message
miked (miked11) wrote :

root@Ubuntu710GustyGibbonBeta:~# G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log metacity --replace

Revision history for this message
miked (miked11) wrote :

added requested valgrind info

Changed in metacity:
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in metacity:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in metacity:
status: Incomplete → Invalid
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.