search

ssanthosh243 / semicomplete

Automatically exported from code.google.com/p/semicomplete
0 stars 0 forks source link

High CPU usage for the WM and inability to select windows #77

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run multiple xdotool commands in a row like so:
sleep 3;for word in this is a test;do xdotool type --delay 0 $word;xdotool key 
KP_Enter;done

2. Try to select a window right after that has finished                         

What is the expected output? What do you see instead?
Desktop is expected to behave normally after xdotool has ran multiple times.

What version of the product are you using? On what operating system?
I am running Debian Stable with 
ii  xdotool                         1:2.20100701.2961-3+ amd64

Please provide any additional information below.

After I run the above command I am unable to select any windows for a period of 
time and openbox my window manager runs at 80%-90% or the CPU.  This normally 
cools off in less then a minute and things start to work normally again.  
However if I string together a lot of xdotool commands it hangs for a long 
while.  I had to restart my xsession to get control of my desktop back once.  
The situation this affects me is when I am calling xdotool from a script.

Original issue reported on code.google.com by gok...@gmail.com on 19 Oct 2013 at 1:07

GoogleCodeExporter commented 9 years ago 
Gok...

Have you made any progress in regards to this issue?   Alternatives or 
workarounds?  I have the same issue and it is rendering my planned use of 
xdotool invalid.

Regards,
Will

Original comment by will.kos...@gmail.com on 22 Dec 2013 at 4:51

GoogleCodeExporter commented 9 years ago 
Unfortunately no, I still have the same problem.  I have not been using xdotool 
as its not near as useful if I have to sit there and wait after its typed in 
everything before I can use the computer again.

Original comment by gok...@gmail.com on 25 Dec 2013 at 1:36

GoogleCodeExporter commented 9 years ago 
Gok:

Thanks for the reply.  Since I asked my question I built a version of xdtool 
from source as the one that was installed from distribution was quite dated. It 
seems to have solved my problem.

Happy Holidays,
Will

Original comment by will.kos...@gmail.com on 25 Dec 2013 at 6:27

GoogleCodeExporter commented 9 years ago 
I pulled in the version from Testing and it works for me now as well.

I am now using:
ii  xdotool                      1:3.20130111.1-3    amd64

I guess this bug can now be closed as its fixed in the recent versions.

Original comment by gok...@gmail.com on 27 Dec 2013 at 1:44