search

Pulover / PuloversMacroCreator

Automation Utility - Recorder & Script Generator
http://www.macrocreator.com
Other
1.66k stars 235 forks source link

CPU Usage doing nothing #178

Closed TheOne010 closed 3 years ago

TheOne010 commented 3 years ago

For some reason MacroCreator.exe uses a fair bit of CPU (10-15%) doing nothing. If a dropdown or context menu is open the load drops to 0,xx%. I have tested 5.4.0 both x64/x86 versions on Windows 10.

Pulover commented 3 years ago

It has its internal processes running like event listeners. Why is it an issue?

TheOne010 commented 3 years ago

Never heard of an application that uses this much only to listen to events, its also weird that it drops to 0,xx% if a dropdown menu is open. It just seems uneccessary causing the CPU fan to speed up, draw more power etc. for just waiting for a key press or something. Is there a way to disable some of these functions?

Pulover commented 3 years ago

There are other processes of course, not only event listeners. But anyway you seem to be having some particular issue. I've started PMC here and while idle its CPU usage stays at 0-0,5%. Even while recording it doesn't go beyond 1,5%. Some operations like dragging rows might consume a lot of CPU indeed, but only while holding the mouse button. I can't think of anything that could be causing this high usage for you, but you can play with settings to see if anything changes.

TheOne010 commented 3 years ago

Ok, i have tested this on another machine and it's not an issue there either. I'll check back if I find out what causes this (if its not an issue with another application). Thank you very much for your support.

Freekmine commented 2 years ago

I am having the same issue. To the extent that it consistently takes 45 seconds for the PMC Settings dialog to open after clicking Options>Settings.

SullieLore commented 2 years ago

This also seems to be happening to me. The program will start by using 0-2% CPU, then spike to 10%+ after 30 or so minutes of editing a script. Multiple scripts tested. Restarting the program doesn't reset the CPU below 10%, but restarting the PC does fix the problem until it starts again around 30 minutes later. Would be great to have a fix, as the program is basically unusable at such high CPU spikes; becomes unresponsive to most UI clicks etc.

faxmbo commented 3 weeks ago

I also encountered the exact same problem