running the atom editor and pressing alt-tab causes compiz to freeze and crash

Bug #1615304 reported by Gonçalo Gomes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Expired
High
Unassigned

Bug Description

Running the atom editor (www.atom.io) on ubuntu 14.04 with gnome-panel + compiz leads to compiz crash when pressing alt-tab to switch to a different window.

Reproduces every time.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu

Description: Ubuntu 14.04.5 LTS
Release: 14.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
compiz:

  Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1
  Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1
  Version table:
 *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0
        500 http://ie.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:0.9.11+14.04.20140409-0ubuntu1 0
        500 http://ie.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

3) What you expected to happen

I expected ctrl-tab to switch me to a different window.

4) What happened instead

The environment freezes, despite mouse still moving. No application or item in the windowing system responds and ultimately compiz crashes (~5 seconds later), leading up to black screen followed by a default graphical login prompt.

This bug is fully reproducible in my environment and I'm eager to help debug it.

Revision history for this message
Gonçalo Gomes (gagomes) wrote :

The same sort of behaviour has been experienced, although not as easily reproducible, when using firefox with multiple open windows spread across different workspaces.

summary: - running atom and alt-tab causes compiz to crash
+ running atom and pressing alt-tab causes compiz to freeze and crash
summary: - running atom and pressing alt-tab causes compiz to freeze and crash
+ running the atom editor and pressing alt-tab causes compiz to freeze and
+ crash
description: updated
description: updated
Gonçalo Gomes (gagomes)
description: updated
description: updated
Revision history for this message
Gonçalo Gomes (gagomes) wrote :
Download full text (30.6 KiB)

I managed to reproduce this under the debugger, however it took several tries for it to reproduce, suggesting this may be a possible race condition.

Furthermore, I have noticed the bug shows itself in the form of either

(1) mouse moves, but no screen updates. A crash ensues within 5-10 seconds
(2) no mouse moves or screen updates. No crash, compiz remains using 100% of cpu (1 core) on the faulting thread.

I gathered some output from gdb and top:

#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x00007f59cab22d25 in ?? () from /usr/lib/nvidia-352/libGL.so.1
#2 0x00007f59cab22a23 in ?? () from /usr/lib/nvidia-352/libGL.so.1
#3 0x00007f59c2d300b3 in ?? () from /usr/lib/nvidia-352/libnvidia-glcore.so.352.63
#4 0x00007f59c2c97b1d in ?? () from /usr/lib/nvidia-352/libnvidia-glcore.so.352.63
#5 0x00007f59c2c98e17 in ?? () from /usr/lib/nvidia-352/libnvidia-glcore.so.352.63
#6 0x00007f59c2c1c5b5 in ?? () from /usr/lib/nvidia-352/libnvidia-glcore.so.352.63
#7 0x00007f59caaf54fe in glXDestroyPixmap () from /usr/lib/nvidia-352/libGL.so.1
#8 0x00007f59cade58b0 in TfpTexture::~TfpTexture() () from /usr/lib/compiz/libopengl.so
#9 0x00007f59cade5919 in TfpTexture::~TfpTexture() () from /usr/lib/compiz/libopengl.so
#10 0x00007f59cade4dcd in GLTexture::List::~List() () from /usr/lib/compiz/libopengl.so
#11 0x00007f59c92fcf49 in DecorTexture::~DecorTexture() () from /usr/lib/compiz/libdecor.so
#12 0x00007f59c92fd010 in DecorScreen::releaseTexture(DecorTexture*) () from /usr/lib/compiz/libdecor.so
#13 0x00007f59c9303f9a in Decoration::~Decoration() () from /usr/lib/compiz/libdecor.so
#14 0x00007f59c9304059 in Decoration::~Decoration() () from /usr/lib/compiz/libdecor.so
#15 0x00007f59c9300b2a in DecorWindow::update(bool) () from /usr/lib/compiz/libdecor.so
#16 0x00007f59c930534b in DecorScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libdecor.so
#17 0x00007f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123
#18 0x00007f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123
#19 0x00007f59c0a85d90 in ResizeLogic::handleEvent(_XEvent*) () from /usr/lib/compiz/libresize.so
#20 0x00007f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123
#21 0x00007f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123
#22 0x00007f59c0650591 in RegexScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libregex.so
#23 0x00007f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123
#24 0x00007f59c043dbad in PlaceScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libplace.so
#25 0x00007f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123
#26 0x00007f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123
#27 0x00007f59bbbe37ee in MoveScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libmove.so
#28 0x00007f59d712773f in CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20140123
#29 0x00007f59d712773f in CompScreen::handleEvent(_X...

Revision history for this message
Gonçalo Gomes (gagomes) wrote :

The only information from perf I found was just this line, which I believe I copied from the `perf top` but not particularly convinced this will be of much help, but hopefully it may be useful in correlating any existing

14.00% libnvidia-glcore.so.352.63 [.] 0x0000000001822cc6 ◈ 11.03% libc-2.19.so [.] syscall ▒

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

Gonçalo, your issue seems to be with the nvidia binary drivers, does it work better if you use "nouveau" instead?

Changed in compiz (Ubuntu):
status: New → Incomplete
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Changed in compiz (Ubuntu):
status: Incomplete → Expired
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.