compiz.real crashed with SIGSEGV in reallocDisplayPrivate()

Bug #281545 reported by David D Short
30
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: compiz

I didn't notice anything crash, but the crash report came up. Several crash reports have come up since I installed “ubuntu-desktop” on my Kubuntu Intrepid machine. I trust that all the necessary information will be added to this report automatically. I'm not going to go back and search for more info to add.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/compiz.real
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.7.8-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --loose-binding core ccp
ProcEnviron:
 PATH=/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: compiz
Stacktrace:
 #0 0x00000000004101ae in ?? ()
 #1 0x0000000000412b25 in eventLoop ()
 #2 0x000000000040d085 in main ()
StacktraceTop:
 ?? ()
 eventLoop ()
 main ()
ThreadStacktrace:
 .
 Thread 1 (process 6434):
 #0 0x00000000004101ae in ?? ()
 #1 0x0000000000412b25 in eventLoop ()
 #2 0x000000000040d085 in main ()
Title: compiz.real crashed with SIGSEGV in eventLoop()
Uname: Linux 2.6.27-4-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Tags: apport-crash
Revision history for this message
David D Short (chameleondave) wrote :
tags: added: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:reallocDisplayPrivate (size=2110790144,
eventLoop () at ../../src/display.c:1765
main (argc=18820225, argv=0x127)

Changed in compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
summary: - compiz.real crashed with SIGSEGV in eventLoop()
+ compiz.real crashed with SIGSEGV in reallocDisplayPrivate()
Revision history for this message
Travis Watkins (amaranth) wrote :

Looking at the stacktrace this appears to be stack corruption as there is no way a crash could happen in that function otherwise. That makes this bug impossible to debug unless someone is able to consistently reproduce it. Is anyone having this problem consistently anymore?

visibility: private → public
Changed in compiz (Ubuntu):
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 compiz (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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