Bug 47216 - upgrade to libxt 1.1.2 breaks "windowless" applications
Summary: upgrade to libxt 1.1.2 breaks "windowless" applications
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/Xt (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard: 2012BRB_Reviewed
Keywords: regression
Depends on:
Blocks: X11R7.7
  Show dependency treegraph
 
Reported: 2012-03-11 22:19 UTC by Norbert Zeh
Modified: 2012-03-12 18:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Norbert Zeh 2012-03-11 22:19:44 UTC
I observed several symptoms:

(1) On my login screen (xdm) I run an xclock.  Upon login, this xclock gets killed using xkill.  Before killing the xclock, all is normal.  Once the xclock window gets killed using xkill, the application sticks around and spins one core at 100%.

(2) My .xinitrc starts an xscreensaver session.  About half the time, xscreensaver immediately starts spinning one of the cores at 100%.

The commonality I observed between these two symptoms is that in both cases, it is an application that currently doesn't have a mapped window that is spinning the CPU.

My system is an up-to-date ArchLinux system with kernel 3.2.9, latest stable xorg (unpatched).  I observed this behaviour both on my desktop system running an NVIDIA NVS 450 and on my laptop with built-in Core i7 graphics.  My logs don't show anything unusual (unless I don't know what to look for).
Comment 1 Jeremy Huddleston Sequoia 2012-03-12 17:53:31 UTC
I'm able to reproduce this.
Comment 2 Norbert Zeh 2012-03-12 18:14:02 UTC
Reverting commit 70bb9e28d37fff4ead4d0a2c672af77059765fa4 in libxt fixes this.  Apparently, this is the same bug as already reported as ID 47203.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.