Script becomes way slower after a msgbox - (Moved)

[Neat]

Hi everyone.

I noticed something very weird on my windows 10 computer.
When the script isn't "graphic" (no msgbox, inputbox, gui etc), the script is relatively fast.
Whenever a script becomes "graphic" (a msgbox was launched) its execution is then 6 times slower.
Here are the results of the execution of this script :

$x=0
$start=TimerInit()
for $i=1 to 500000
    $x+=1
Next
MsgBox(0,"",TimerDiff($start)) ;160ms => becoming slower now because of the msgbox

$start=TimerInit()
$x=0
for $i=1 to 500000
    $x+=1
Next
MsgBox(0,"",TimerDiff($start)) ;1300ms

I tried on my windows 7 computer and the bug isn't there.
I tried everything and it really comes to this => whenever something graphic has been prompted, even if it's over, the script is way slower then.

Can someone try to reproduce this? And how do I report a bug?

[TheXman]

First, why did you post this in the "AutoIt Projects and Collaboration" forum?  This has nothing to do with a project or a collaboration.

 

I do not get any large differences between the 2 loops when I execute your code:

$x=0
$start=TimerInit()
for $i=1 to 500000
    $x+=1
Next
ConsoleWrite("Loop 1 Elapsed time: " & TimerDiff($start) & @CRLF)

$x=0
$start=TimerInit()
for $i=1 to 500000
    $x+=1
Next
ConsoleWrite("Loop 2 Elapsed time: " & TimerDiff($start) & @CRLF)

Output:

Loop 1 Elapsed time: 64.3125556633415
Loop 2 Elapsed time: 64.5393475676982

 

[Nine]

Confirmed.  on Win10 the scale is similar as yours 10x slower after the MsgBox.  On Win7 no impact.

[seadoggie01]

Win10 Enterprise shows similar results after the MsgBox. Interestingly, subsequent loops have the same speed as the second loop, never reverting to the original speed.

[Nine]

@TheXman  Yes as with you, using ConsoleWrite has no impact

[TheXman]

LOL, yes I just noticed that. 

I see the same discrepancies, as the original post, when I execute the script with MsgBox,

Edited April 2, 2020 by TheXman

[Nine]

Tested with a GuiCreate, after show and even GuiDelete, same phenomenon...

[Jos]

Moved to the appropriate forum.

Moderation Team

[Nine]

Interesting enough, if you replace the MsgBox with this line then the phenomenon disappear :

RunWait (@AutoItExe & ' /AutoIt3ExecuteLine "MsgBox(4096, ''Hello World!'', ''Hi!'')"')

 

[seadoggie01]

No that makes sense (I think), everything gets garbage collected after the executed line exits and it's all in another process so it doesn't matter to the current process

[Nine]

Yes, I know but I found it interesting to notice, that the process is not corrupted by the appearance of a GUI, but it is intrinsic to its own process.

[jchd]

Only Devs can tell but isn't the issue related to the various hooks or message interceptions that AutoIt core has to setup before any GUI operation, which aren't needed until the first GUI is invoked.

But why is Win 10 different from Win 7 in this aspect is a mystery to me.

[Jos]

14 minutes ago, jchd said:

Only Devs can tell but isn't the issue related to the various hooks or message interceptions that AutoIt core has to setup before any GUI operation

I doubt this, without having looked at it in detail in the source, but AutoIt3 always has a background GUI running to be able to work with the Windows Messages.
A call to MSGBOX is really a standard DLL call to MessageBoxW. ....  maybe one could try using that to see if that is similar?

 

[Neat]

Thank you all for your answers, and sorry for posting on the wrong forum, that's my first post.

Do I need to do anything for the devs to know about it? Or you guys handle that?

Btw my guess was : whenever the script display something (even once) it suddenly gets different from a "classical script" (as you said different hooks etc), maybe windows 7 manages to get back to a classic execution, and windows 10 doesn't.

Knowing that, executing the msgbox through another script solves it, thanks for your trick !

I hope it's gonna be solved soon (or a work around) because it means you can never have both a quick script and displaying windows on windows 10..

[Nine]

@Jos is right.  Tested all the MessageBox and MessageBoxEx, the same behavior appears.  Seems it is more of a Win10 problem (again). Sigh...

[jchd]

Ouch!

It's surprising that others applications don't seem to exhibit that slow behavior under W10, at least I can't find any significantly slower app under W10 than W7 and on the contrary, I feel my rig more responsive (I upgraded just recently).

[jchd]

SplashTextOn() doesn't slow things...

MsgBox() slows by factor 6 for me!  That's something!

EDIT: MsgBox() still slows thing by 6 in compiled CUI scripts...

Edited April 2, 2020 by jchd

[Nine]

By killing dwm.exe I cut by more than 3 the slowness effect.  It is still 3 times slower after showing the MsgBox but it is an improvement...

[Neat]

Here's a function to avoid the issue (also allows a non-blocking msgbox).
It's an ugly version but I'm sure you guys will improve it

Func MsgBox_ext($type = 0, $title = "", $txt = "", $block = 1)
    $txt = StringRegExpReplace($txt, "('|" & '")', "$1$1")
    $type = StringRegExpReplace($type, "('|" & '")', "$1$1")
    $title = StringRegExpReplace($title, "('|" & '")', "$1$1")
    If $block <> 1 Then
        Return Run(@AutoItExe & ' /AutoIt3ExecuteLine "' & "MsgBox('" & $type & "','" & $title & "','" & $txt & "')" & '"')
    Else
        Return RunWait(@AutoItExe & ' /AutoIt3ExecuteLine "' & "Exit(MsgBox('" & $type & "','" & $title & "','" & $txt & "'))" & '"')
    EndIf
EndFunc   ;==>MsgBox_ext

 

[Nine]

Could someone test the same with C++ on Win10 ?   Thanks.