1

Running cygwin/X I see at-spi-bus-launcher and xwin-xdg-menu are using most of the cpu. There are two instances of xwin-xdg-menu.

Between the three of them there isn't much left for anything else. How can I fix this?

enter image description here

1
rm -r ~/.dbus*

Then start XWin

If it's still stuck, open task manager and see if there are 2 XWin.exe processes kill the one with lower memory usage

  • I think I have seen two XWin processes. I will try this next time. – Miserable Variable May 25 '17 at 19:04
1

Solution:
Create a ~/.startxwinrc file, and add one line:

exec sleep infinity

Make ~/.startxwinrc executable by running chmod +x ~/.startxwinrc.

Reason I suspect this worked:
startxwin searches for a ~/.startxwinrc file to execute when launching. If startxwin does not find a ~/.startxwinrc file, startxwin will follow the default routine outlined in /etc/X11/xinit/startxwinrc.

The default routine launches /usr/bin/xwin-xdg-menu, somehow causing me to have two xwin-xdg-menu processes, one of them with very high cpu. Creating ~/.startxwinrc bypasses the default routine, disabling /usr/bin/xwin-xdg-menu from launching altogether.

exec sleep infinity keeps the x server alive after launching.

(This response is a copy from my solution to a similar question)

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.