Modify

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#3277 closed Bug (Duplicate)

_IEFrameGetObjByName crashes Script after many uses on Win7 and newest AutoIt Version v3.3.14.2

Reported by: ixam Owned by:
Milestone: Component: AutoIt
Version: 3.3.14.2 Severity: None
Keywords: Bug, Memory Leak, _IEFrameGetObjByName, crash Cc:

Description

First of all here is the Forum post I made:
https://www.autoitscript.com/forum/topic/184469-ie-functions-throw-error-after-many-calls-in-a-while-loop

Anyway I´ll summarize when you execute this example script:

#include <ie.au3>


Local $oIE = _IE_Example("iframe")
Local $oFrame
Local $i=0
Local $tdStart=TimerInit()
While 1
    Local $oFrame = _IEFrameGetObjByName($oIE, "iFrameTwo")
    $i+=1
    If Not Mod($i,10) Then
    ConsoleWrite($i&@CRLF)
    Sleep(1)
    EndIf
    If $i>10000 Then ExitLoop
WEnd
ConsoleWrite(TimerDiff($tdStart)&@TAB&$i& ' Times looped'&@CRLF)
_IEQuit($oIE)

I could test this script on 2 Windows 7 PCs and 1 Windows 10 PC,
the Script crashes on both Windows 7 PCs, but not on the Windows 10 PC (all with up to date IE). But I found out it only happens with the newest Version of Autiot v3.3.14.2. If I compile the Script with v3.3.12.0 it never crashes on any PC.
The Error Message in the Console is as follows:

"C:\Program Files (x86)\AutoIt3\Include\ie.au3" (1811) : ==> The requested action with this object has failed.:
Return SetError($_IESTATUS_Success, $oTemp.GetElementsByTagName($sTagName).length, $oTemp.GetElementsByTagName($sTagName))
Return SetError($_IESTATUS_Success, $oTemp^ ERROR
->12:16:20 AutoIt3.exe ended.rc:1

Attachments (0)

Change History (4)

comment:1 by mLipok, 9 years ago

Resolution: Duplicate
Status: newclosed

comment:2 by mLipok, 9 years ago

btw.
This problem probably will be fixed in next IE.au3 version.
But for now you should keep eye on ticket #3167

.... and you should read this:
https://www.autoitscript.com/forum/topic/177783-example-proper-usage-ieau3-udf-with-autoit-v3314x/

Last edited 9 years ago by mLipok (previous) (diff)

comment:3 by anonymous, 9 years ago

I can confirm that an Win 7 v3.3.14.2 exits with the same error as above.
When using an own Error Handler as proposed I get this output:

: ==> COM Error intercepted !

err.number is: 0x80020008
err.windescription: Bad variable type.

err.description is:
err.source is:
err.helpfile is:
err.helpcontext is:
err.lastdllerror is: 0
err.scriptline is: 1811
err.retcode is: 0x00000000

: ==> COM Error intercepted !

err.number is: 0x80020008
err.windescription: Bad variable type.

err.description is:
err.source is:
err.helpfile is:
err.helpcontext is:
err.lastdllerror is: 0
err.scriptline is: 1811
err.retcode is: 0x00000000

: ==> COM Error intercepted !

err.number is: 0x000000A9
err.windescription: Variable is not of type 'Object'.
err.description is:
err.source is:
err.helpfile is:
err.helpcontext is:
err.lastdllerror is: 0
err.scriptline is: 152
err.retcode is: 0x00000000

: ==> COM Error intercepted !

err.number is: 0x80020008
err.windescription: Bad variable type.

err.description is:
err.source is:
err.helpfile is:
err.helpcontext is:
err.lastdllerror is: 0
err.scriptline is: 1811
err.retcode is: 0x00000000

: ==> COM Error intercepted !

err.number is: 0x80020008
err.windescription: Bad variable type.

err.description is:
err.source is:
err.helpfile is:
err.helpcontext is:
err.lastdllerror is: 0
err.scriptline is: 1811
err.retcode is: 0x00000000

: ==> COM Error intercepted !

err.number is: 0x000000A9
err.windescription: Variable is not of type 'Object'.
err.description is:
err.source is:
err.helpfile is:
err.helpcontext is:
err.lastdllerror is: 0
err.scriptline is: 193
err.retcode is: 0x00000000

comment:4 by anonymous, 9 years ago

Tested it with version v3.3.12.0, it does not happen there.

Modify Ticket

Action
as closed The ticket will remain with no owner.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.