raghuram534 / autokey

Automatically exported from code.google.com/p/autokey
GNU General Public License v3.0
0 stars 0 forks source link

100% CPU usage + system freeze #73

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Often, Autokey is using 100% of my CPU and I must kill it.
It often freeze the display when I edit some script and I need to use the 
second display for kill it (Ctrl+Alt+F6).

AutoKey (GTK) 0.71 on Ubuntu 10.04.
Python 2.6.5.

Hoping I was understable.

Original issue reported on code.google.com by ggauthie...@gmail.com on 19 Aug 2010 at 3:46

GoogleCodeExporter commented 8 years ago
Can you try adding the attached autokey script (by importing) and running it 
when you see the 100% cpu usage? You can run it by selecting it from the 
AutoKey tray menu. It puts information on your system clipboard, which you can 
then paste into this bug. Thanks.

Original comment by cdekter on 20 Aug 2010 at 5:45

Attachments:

GoogleCodeExporter commented 8 years ago
I can't run any script when i see 100% cpu usage.
But I can get the traceback in a terminal (see attached file "traceback.txt") 
after I close it (display freeze only when I edit a script).

I noticed that AK is looping on a script execution of the last script ran, a 
number of times before using 100% of my cpu. And it use approximately 50% of my 
cpu on two thread (my two core are used, thank to conky I can easily see this) 
while it is on one thread when it use 100% of my cpu.

Original comment by ggauthie...@gmail.com on 20 Aug 2010 at 7:57

Attachments:

GoogleCodeExporter commented 8 years ago
Unfortunately that traceback doesn't really provide any useful info. If AutoKey 
is looping on a script, I would suggest that the problem is in your script.

Original comment by cdekter on 20 Aug 2010 at 10:24

GoogleCodeExporter commented 8 years ago
I wanted to say that the script is executed several times.
I think there is more execution than shortcut press.

And in all my script, there isn't any loop, no "for", no "while".
I juste overwrite the key send under certain condition.

Original comment by ggauthie...@gmail.com on 20 Aug 2010 at 10:37

GoogleCodeExporter commented 8 years ago
Can you post the script here?

Original comment by cdekter on 20 Aug 2010 at 12:23

GoogleCodeExporter commented 8 years ago
I think I found the problem.

Look at the script named "vol+". It get the map and call Map.volPlus() (see 
aklib.py, at start, the map is Map) witch send "<code123>" wich is the shorcut 
for the vol+ script...
On the first key press, the script is executed one time but the second key 
press it is executed several time and often loop on this execution.
Once I pressed the vol+ shortcut, it use 100% of my cpu if I press any key. But 
it not always loop on the vol+ execution.

But this does not occur with others shortcut wich have the same principle 
including "vol-".

For details, I use those script for the remote control of my TNT tuner 
(Pinnacle PCTV Nanostick).

Original comment by ggauthie...@gmail.com on 20 Aug 2010 at 2:41

Attachments:

GoogleCodeExporter commented 8 years ago
In your aklib.py, can you try using keyboard.fake_keypress() instead of 
keyboard.send_key()?

Original comment by cdekter on 20 Aug 2010 at 2:51

GoogleCodeExporter commented 8 years ago
Same problem.

it's stange that this occur only with "vol+".

Original comment by ggauthie...@gmail.com on 20 Aug 2010 at 3:28

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
The Gnome volume applet does something strange with faking keypresses to adjust 
the volume. This bug is caused by that behaviour so there is nothing I can do 
about it.

Original comment by cdekter on 3 Oct 2010 at 1:04

GoogleCodeExporter commented 8 years ago

 Hi.

 I'm suffering the same problem in Ubuntu 10.10. I always leave the computer switched on at work, and sometimes, when I arrive the next morning, autokey-gtk is taking 50-100% CPU, while the previous day I had no problem. Notice that raises from 0% to 100% with no usage (at nigth, when I'm not using the computer).

 I only have simple substitution macros (replaces) configured, and the "sample scripts". I'm "deleting" the sample scripts today to see if it happens again only with my 3 substituion macros.

Original comment by srom...@gmail.com on 3 Feb 2011 at 7:10