compiz crashed with signal 5 in Glib::exception_handlers_invoke()

Bug #981402 reported by Sepero
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

Apologies in advance if this has been reported already. Compiz seems to lockup every day now.
Steps to reproduce:
1. Go to sleep (leave)
2. Monitor gets turned off automatically after 10min
3. Come back about 10 hours later and move mouse/press keys
4. The screen comes on, but shows the mouse hovering over an all black screen
5. Press Ctrl+Alt+F1 and run top
6. See that compiz is using high amount of cpu
7. Wait 10minutes
8. See that compiz is still using high amount of cpu
9. Alt+F7 shows the desktop remains the same
10. Compiz appears to be in an infinite loop, so I try to kill it
11. Kill level -15 does not work, so I kill it level -9
12. Compiz restarts, and the desktop is recovered with all programs intact (thank you)

Note: I have a script that is constantly running partprobe, fdisk, and truecrypt in the background specifically when the screensaver comes on. I have all output from them sent to log files, and I'm not noticing any abnormal errors. I don't know if compiz might be susceptible crashing from partition changes or not, but I think I started noticing this problem around the time I implemented that script. Tomorrow I will turn the background script off and see if compiz still crashes.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
Uname: Linux 3.2.0-22-generic-pae i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module 295.33 Sat Mar 17 14:56:23 PDT 2012
 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4)
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,resize,grid,expo,gnomecompat,scale,place,move,workarounds,regex,mousepoll,snap,session,vpswitch,neg,wall,unityshell]
CompositorRunning: compiz
CrashCounter: 1
Date: Sat Apr 14 02:32:33 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current, 295.40, 3.2.0-22-generic-pae, i686: installed
 nvidia-current, 295.40, 3.2.0-23-generic-pae, i686: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Device [196e:066d]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
JockeyStatus:
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 003 Device 002: ID 0d8c:0008 C-Media Electronics, Inc.
MachineType: Gateway W3410
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic-pae root=UUID=acbe3514-33a3-4170-b1be-df7b8460a49a ro quiet splash vt.handoff=7
Signal: 5
SourcePackage: compiz
StacktraceTop:
 Glib::exception_handlers_invoke() () from /usr/lib/i386-linux-gnu/libglibmm-2.4.so.1
 Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/i386-linux-gnu/libglibmm-2.4.so.1
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with signal 5 in Glib::exception_handlers_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/06/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7145
dmi.board.vendor: MICRO-STAR
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/06/2005:svnGateway:pnW3410:pvr:rvnMICRO-STAR:rnMS-7145:rvr:cvn:ct3:cvr:
dmi.product.name: W3410
dmi.sys.vendor: Gateway
version.compiz: compiz 1:0.9.7.6-0ubuntu1
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

Revision history for this message
Sepero (cowpie2000) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #964316, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
Sepero (cowpie2000) wrote :

"Remember, this bug report is a duplicate of a private bug. Comment here only if you think the duplicate status is wrong. "
How am I supposed to know if the duplicate status is wrong if I'm unable to view the private bug??

Revision history for this message
Sepero (cowpie2000) wrote :

Last night I let my computer run without my partitioning script running, and this morning compiz did not crash or freeze. I'm going to do the same again tonight and see if the results are the consistent. If so, then I will isolate parts of my script and try to discover what is afflicting compiz.

Revision history for this message
Sepero (cowpie2000) wrote :

I would have replied sooner, but I've been having health problems. Moving on...

When I did not run my script for 4 days, compiz did not "lockup" in an infinite loop.

Last night I ran a part of my script throughout the night (about 8 hours). When I woke up, I exited my script (on terminal F1) and waited several minutes. Again compiz appeared to be "lockedup" in an infinite loop.

All my partial script did was continuously run partprobe.

while true; do
partprobe /dev/sda
done

In conclusion, it appears that compiz is not playing nicely with partprobe.

Revision history for this message
Sepero (cowpie2000) wrote :

Another Test! I ran this script on my system while actively using it (doing other things/browsing)

#!/usr/bin/env bash
while true; do
  partprobe /dev/sda
  sleep 5
done

Perhaps someone else could test this themselves. My results are that my system becomes progressively less and less responsive, and more and more consumed with the partprobe process. In about an hour, the partprobe process goes from a mild annoyance, to completely unbearable.

Note: If I leave the script running (for example, on terminal F1), log out of gnome-session, then log back in- all responsiveness is returned.

Though, after logging back in, continuing to leave the script running will eventually take all system responsiveness down again.

When the responsiveness was down, I checked the cpu comsumption with top. It reveals compiz comsuming giant amounts processor time.

PS.
Are there any moderators seeing my reports here? Does this bug appear to be a duplicate?? I'm forbidden from seeing the report that mine has been marked a "duplicate of".

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.