Ticket #241 (closed usability: fixed)

Opened 5 years ago

Last modified 4 years ago

xquarz uses 100% of CPU when not focused

Reported by: knussear@… Owned by: jeremyhu@…
Priority: Important Milestone: 2.3.3
Component: xserver Version: 2.3.2 (xserver-1.4.2-apple31)
Keywords: Cc: ch.wolf@…, ukasc@…, tofergregg@…, cleanthes@…

Description

I'm using xquartz 2.3.2.1 on osx 10.5.6 on a 2.16 GHz intel core 2 duo. When x11 is running, but is not focused it begins to use 100% of my cpu until re-focused.

Repeatable 100% of the time.

Attachments

xq2.3.2.1 sample.txt (12.3 KB) - added by knussear@… 5 years ago.
sample taken during 100% cpu usage

Change History

Changed 5 years ago by knussear@…

sample taken during 100% cpu usage

comment:1 Changed 5 years ago by jeremyhu@…

  • Priority changed from critical to major
  • Milestone set to 2.4.0

Please join xquartz-dev to discuss this... I can't reproduce it.

comment:2 Changed 5 years ago by knussear@…

OK posted on the dev

comment:3 Changed 5 years ago by lukasc@…

I have the same problem, except that on mine it is using only 1 CPU (out of 2), hence 50%. Exactly the same symptom - cpu used when switched to another application, ~0% when on X11.app.

comment:4 Changed 5 years ago by jeremyhu@…

  • Cc ch.wolf@…, ukasc@… added

Chris narrowed this down to: 0012-XQuartz-Only-send-mouse-events-while-in-the-backgro.patch

comment:5 follow-up: ↓ 6 Changed 5 years ago by jeremyhu@…

What kind of input devices do you guys have on your systems?

comment:6 in reply to: ↑ 5 Changed 5 years ago by knussear@…

Replying to jeremyhu@…:

What kind of input devices do you guys have on your systems?

Just a laptop with a trackpad, but also when I have a bluetooth mouse paired.

comment:7 Changed 5 years ago by lukasc@…

I have a MacBook Pro with regular trackpad (~2 years old). OS 10.5.6.

comment:8 Changed 5 years ago by xquartz@…

I am experiencing exactly the same thing. I have a Mac book pro, with leopard version 10.5.6 and the latest version of xquartz. I use a Wacom pen tablet pretty continuously, so I've only just tested it without a pen tablet plugged in. So far, the problem does NOT appear when the pen tablet is not plugged in.

comment:9 in reply to: ↑ description Changed 5 years ago by tofergregg@…

Exactly the same problem here. 100% cpu usage (as reported by top) on one core when X11 is in the background. Makes the fans on my Leopard 10.5.6 Macbook run like crazy.

comment:10 Changed 5 years ago by tofergregg@…

  • Cc tofergregg@… added

Cc Me!

comment:11 Changed 5 years ago by jeremyhu@…

You should not be seeing it in 2.3.3_beta1 ... I commented out the code that Chris bisected down to.

comment:12 Changed 5 years ago by jeremyhu@…

  • Milestone changed from 2.3.3 to 2.4.0

comment:13 Changed 5 years ago by lukasc@…

Seems fixed to me! Thank you. (2.3.3_beta1)

Lukas

comment:14 Changed 5 years ago by cleanthes@…

I'm experiencing this problem, too. Where can I download 2.3.3 beta1?

comment:15 Changed 5 years ago by jeremyhu@…

comment:16 Changed 5 years ago by cleanthes@…

Thank you very much.

FWIW, I think everything was ok with 2.3.2.1 until I updated one of my unix packages via fink. Which package? I have no idea. I usually use the update-all command with fink, thus updating as many as 20 packages at a time. I primarily run gnucash and pan, which require the gnome desktop. So, I'm tempted to say that the problem started with one of the gnome components.

comment:17 Changed 5 years ago by cleanthes@…

  • Cc cleanthes@… added

Cc Me!

comment:18 Changed 5 years ago by cleanthes@…

I installed 2.3.3 RC5 last night, and as of now, this bug is back. It was gone in RC2.

comment:19 Changed 5 years ago by jeremyhu@…

Well then you are hitting a different bug. Please open a new report and provide a sample of the running process in this configuration and your org.x.X11 preferences. The code that Chris narrowed this down to is commented out, so this is probably something else. What is showing up in Activity Monitor? (answer in your new bug)

comment:20 Changed 5 years ago by jeremyhu@…

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from 2.4.0 to 2.3.3

Chris mentioned that this is indeed the same bug, so the underlying issue is actually something else. I've debugged it and have the fix in git.

comment:21 Changed 4 years ago by jeremyhu@…

Note: See TracTickets for help on using tickets.