Hi!
In version 11 I get about 50% CPU when I run a compiled machro with one line:
WaitWindowOpen>foo
If I compile the same thing in version 9 i get 0% CPU
* Is it only me that has this?
* Is there a way to fix this?
* Is it the same for version 10 and 12?
Thanks!
WaitWindowOpen> very CPU hungry
Moderators: JRL, Dorian (MJT support)
-
- Pro Scripter
- Posts: 149
- Joined: Tue Mar 23, 2004 9:11 pm
I tried versions 9, 10, 11 and 12 and got 0% CPU usage on all of them. Although for some reason under version 10 when I first start the script the CPU jumps up to 3% for about 5 seconds. The version 11 build that I have installed is 11.1.17. Perhaps that makes a difference. Which build are you running?
-
- Pro Scripter
- Posts: 149
- Joined: Tue Mar 23, 2004 9:11 pm
-
- Pro Scripter
- Posts: 149
- Joined: Tue Mar 23, 2004 9:11 pm
-
- Pro Scripter
- Posts: 149
- Joined: Tue Mar 23, 2004 9:11 pm
-
- Pro Scripter
- Posts: 149
- Joined: Tue Mar 23, 2004 9:11 pm
I had significant performance issues starting with MS 11.1.17. There was a fix applied that :
"Fixed: Window commands - if wildcard not specified child/MDI windows would not be found"
In my scripts I was using several OnEvent>WINDOW_OPEN commands. Once these commands were executed, everything slowed down with MS 11.1.17 and above and also MS 12. I had no performance issues with MS 11.1.16 and earlier.
In my case, a workaround was to replace the OnEvent>WINDOW_OPEN commands with OnEvent>WINDOW_NEWACTIVE. I had no performance issues once I made that change regardless of MS version.
I don't know if this has anything to do with your problem or not
...just thought I would share my experience.
"Fixed: Window commands - if wildcard not specified child/MDI windows would not be found"
In my scripts I was using several OnEvent>WINDOW_OPEN commands. Once these commands were executed, everything slowed down with MS 11.1.17 and above and also MS 12. I had no performance issues with MS 11.1.16 and earlier.
In my case, a workaround was to replace the OnEvent>WINDOW_OPEN commands with OnEvent>WINDOW_NEWACTIVE. I had no performance issues once I made that change regardless of MS version.
I don't know if this has anything to do with your problem or not
