Bug 91234

Summary: Xorg process begins consume 100% CPU in AvailableID()
Product: xorg Reporter: mikhail.v.gavrilov
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg backtrace
none
dmesg
none
Xorg.log none

Description mikhail.v.gavrilov 2015-07-05 16:19:51 UTC
Created attachment 116956 [details]
Xorg backtrace

Xorg process begins consume 100% CPU and GUI begins stuck
Comment 1 mikhail.v.gavrilov 2015-07-05 16:20:43 UTC
Created attachment 116957 [details]
dmesg
Comment 2 mikhail.v.gavrilov 2015-07-05 16:23:39 UTC
[root@localhost ~]# rpm -qa | grep Xorg
xorg-x11-server-Xorg-1.17.2-1.fc22.x86_64
[root@localhost ~]# rpm -qa | grep intel
xorg-x11-drv-intel-debuginfo-2.99.917-12.20150615.fc22.x86_64
xorg-x11-drv-intel-2.99.917-12.20150615.fc22.x86_64
xorg-x11-drv-intel-devel-2.99.917-12.20150615.fc22.x86_64
Comment 3 mikhail.v.gavrilov 2015-07-05 16:28:38 UTC
Created attachment 116958 [details]
Xorg.log
Comment 4 Chris Wilson 2015-07-05 17:24:14 UTC
You have a client resource leak if it is looping in AvailableID. Double check that it is indeed stuck there and not just for that one sample. (Similarly perf would be good to check.)
Comment 5 GitLab Migration User 2018-12-17 17:31:20 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/609.

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.