This is the mail archive of the
mailing list for the Cygwin project.
Re: High cpu usage by at-spi-bus-launcher and xwin-xdg-menu
When I kill xwin-xdg-menu the X server does not exit. I have often
found the X applications menu to not appear at startup at all, I will
check next time if that correlates with high cpu.
I will also check ~/.xsession-errors next time this happens.
Right now I do not have at-spi-bus-launcher running, xwin-xdg-menu
takes very little cpu and its menu is present in the notification
I start X as follows, in a .bat file:
C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec
On Wed, May 24, 2017 at 8:32 PM, Jon Turney wrote:
> On 22/05/2017 14:39, miserable variable wrote:
>> I regularly see these two processes taking more that 25% CPU Time
>> each, as reported by ProcessExplorer.
> This shouldn't be happening.
>> I have often terminated both not been able to notice any functionality
>> lost, but I am sure I am missing something.
> I would expect killing xwin-xdg-menu to cause the X server to exit, and it's
> X applications menu to disappear from the notification area.
> I'm not sure if you mean that doesn't happen, or it does but you don't
>> Is there something in my setup causing this?
>> I have attached /var/log/XWin.0.log and output from cygcheck -s -v -r.
>> The latter is quite big and exceed maximum size for this list, I have
>> deleted lines matching 'missing.*python2' of which there were many to
>> stay within the limit.
> Thanks. This doesn't show any problems I can see.
> You might also take a look at ~/.xsession-errors to see if that shows
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple