AutoIt crash with Objects

[mLipok]

Here is repro script:

#include <IE.au3>

_IEErrorHandlerRegister()
_Example()

Func _Example()
	Local $oIE = _IECreate()
	For $iCounter = 1 To 30000
		ConsoleWrite("! " & $iCounter & @CRLF)
		_IEGetObjById($oIE, 'SomeId')
	Next
	_IEQuit($oIE)
EndFunc   ;==>_Example

Exit code:

!>16:45:25 AutoIt3.exe ended.rc:-1073741819
+>16:45:25 AutoIt3Wrapper Finished.
>Exit code: 3221225477    Time: 23.4

[mLipok]

it looks similar to this:
​https://www.autoitscript.com/trac/autoit/ticket/2541

[mLipok]

There is no error if
"c:\Program Files (x86)\AutoIt3\AutoIt3_x64.exe"
is used.

Error occurs only with:
"c:\Program Files (x86)\AutoIt3\AutoIt3.exe"

And here can be usefull information:
​https://www.autoitscript.com/forum/topic/174281-autoit-error-in-ie11/?do=findComment&comment=1277637

After some more research I finally find this:

https://github.com/enthought/comtypes/issues/66

http://permalink.gmane.org/gmane.comp.python.comtypes.user/616

Looks like IE Object related problem  -- Quite possible this is DevEnvironment Independend.
More for OS arch related problem.

EDIT:
My testing System is
Win 7 Pro 64BIt
IE 11.0.9600.18059

[mLipok]

Further discussion in MVP Forum:
​http://www.autoitscript.com/forum/index.php?showtopic=178585

[anonymous]

is there any beta that addresses this issue?

or is reversion to 3.3.12 the only mitigation?

or is there some other mitigation?

[mLipok]

When it be fixed, it will be notified here.
You should wait for fixing.

[anonymous]

+? does using the 64bit compiler completely resolve this issue?
"c:\Program Files (x86)\AutoIt3\AutoIt3_x64.exe"

[anonymous]

I suppose it is obvious,
but,
I tried compiling on a 64bit installation,
but,
with
#AutoIt3Wrapper_UseX64=N
it failed on an x86 windows 7 32bit machine at 316 iterations
then
it failed on an x64 - 64bit windows 7 machine also at 316 iterations.

Is there any hope that this will be fixed on 32 bit machines?
or, should we resign ourselves to either:
1) using a 64bit machine
2) staying back at 3.3.12?

thanks - sorry to be pest ; would like to plan for a future large time investment.
Phil

ps - is this really "fixed" by x64 or is the memory space simply so large that the error doesn't occurr...?

[Jpm]

Hi,
It works for me with the current release

[mLipok]

I think this was fixed somehow in Windows10,
For now Im not able to check in Windows7, how you was testing in Win7 32Bit