Compiler Issue with /NOSTOPKEY with V. 11.1.14 and 11.1.13

Rain · Post by **Rain** » Thu Sep 24, 2009 2:47 pm

There is a problem when compiling scripts with /NOSTOPKEY
When compiling the script below, it takes 7 seconds to run without /NOSTOPKEY versus 104 seconds with /NOSTOPKEY

I don't have this problem with v. 10.018

Can someone confirm this?

Code: Select all

VBSTART
VBEND
VBEval>Timer,startSeconds
wait>1
VBEval>Timer-%startSeconds%,elapsedSeconds
msg>Time Elapsed: %elapsedSeconds%
wait>1
VBEval>Timer-%startSeconds%,elapsedSeconds
msg>Time Elapsed: %elapsedSeconds%
wait>1
VBEval>Timer-%startSeconds%,elapsedSeconds
msg>Time Elapsed: %elapsedSeconds%
wait>1
VBEval>Timer-%startSeconds%,elapsedSeconds
msg>Time Elapsed: %elapsedSeconds%
wait>1
VBEval>Timer-%startSeconds%,elapsedSeconds
msg>Time Elapsed: %elapsedSeconds%
wait>1
VBEval>Timer-%startSeconds%,elapsedSeconds
msg>Time Elapsed: %elapsedSeconds%
wait>1
VBEval>Timer-%startSeconds%,elapsedSeconds

mdl>Total Time Elapsed: %elapsedSeconds%

Thanks,
Rain

Post by **Marcus Tettmar** » Thu Sep 24, 2009 4:04 pm

Odd. I just compiled two versions of that script, with and without /NOSTOPKEY and didn't notice any difference. Ran them both a few times and averaged about 7 seconds for each.

JRL · Post by **JRL** » Thu Sep 24, 2009 4:31 pm

I'm getting similar results as Rain. Mine processed in 92 seconds... I must have a speed demon computer ehhh...

When failing (compiled with NOSTOPKEY) the message sits at 1 second for 80 some seconds then processes the rest of the messages at expected intervals.

Win XP sp3 MS ver. 11.1.14

Rain · Post by **Rain** » Thu Sep 24, 2009 8:55 pm

I don't have the problem with the following versions:
11.1
11.0.05
11.1.08a
11.1.09

I don't have:
11.1.10
11.1.11
11.1.12

So, I can't tell when the problem started but I hope this info will give you guys a starting point to track the bug down.

For now I'm keeping 11.1.09 until this can be fixed.

PS my system info is in my signature.

Post by **Marcus Tettmar** » Fri Sep 25, 2009 8:23 am

Ok, I can replicate in XP, but not in Vista or Windows 7.

I'm at a loss to explain this. Especially since /NOSTOPKEY *prevents* the script from creating a hot key handler. One might theorise that NOT having a hotkey handler would make it faster, not slower, since there would be less work to do. I can't therefore see why including /NOSTOPKEY would slow it down.

So, anyway, yet another unusual, bizarre and esoteric oddity to hunt down. Keeps me off the streets I guess. Sigh.

Rain · Post by **Rain** » Fri Sep 25, 2009 12:38 pm

The CPU usage goes way up. It's as if the exe is stuck in a tight loop. It's about 25 when compiled with /NOSTOPKEY as to 0-1 when compiled without /NOSTOPKEY on my system.

Post by **Marcus Tettmar** » Fri Sep 25, 2009 1:27 pm

Ok, this is now fixed in dev.

jpuziano · Post by **jpuziano** » Fri Sep 25, 2009 9:08 pm

mtettmar wrote:So, anyway, yet another unusual, bizarre and esoteric oddity to hunt down. Keeps me off the streets I guess. Sigh.

Its not so bad... What doesn't kill you, makes you.. and the product... and all of us stronger...

mtettmar wrote:Ok, this is now fixed in dev.

Woot! Keep those maintenance releases coming...

Thanks Rain for reporting this.

Rain · Post by **Rain** » Mon Sep 28, 2009 5:30 pm

That's great news. Can't wait for the next update.