So our theory is that the Flash JIT compiler is getting spoofed
because our event handlers are stored as dynamic properties on
instances rather than being declared as methods. The first time
through the code is likely interpreted and works, the second time
through it is probably trying to execute out of the JIT cache and
puking (because there is no such method).
On 2008-01-09, at 23:43 EST, Henry Minsky wrote:
Google turns up this helpful tidbit
http://kb.adobe.com/selfservice/viewContent.do?externalId=4a146409&sliceId=1
Common Flex 2 compiler errors and known issuesIssue
*175465:* The following runtime error is produced because the
compiler fails
to report an error when there is a protected set method in base
class with
the same name as a protected member variable in a derived class:
VerifyError:
Error #1107: The ABC data is corrupt, attempt to read out of bounds.
On Jan 9, 2008 11:39 PM, Henry Minsky <[EMAIL PROTECTED]> wrote:
I'm usually debugging using the fdb utility, which is a standalone
flash
debug player.
I tried loading up the app I am hacking in firefox, and it was
behaving
differently; After the first time I clicked, the "parent"
was no longer animating it's rotation. The app continued but this
handler
seemed broken.
I installed the debug version of the flash player for Firefox and
ran the
app, and saw this message print out
VerifyError: Error #1107: The ABC data is corrupt, attempt to read
out of
bounds.
at LzEvent/sendEvent()[C:\Documents and Settings\hqm\Local
Settings\Temp\lzswf9\lzgen59453\LzEvent.as:53]
at LzView/mouseevent()[C:\Documents and Settings\hqm\Local
Settings\Temp\lzswf9\lzgen59453\LzView.as:353]
at LzModeManager$/handleMouseEvent()[C:\Documents and
Settings\hqm\Local Settings\Temp\lzswf9\lzgen59453\LzModeManager.as:
74]
at LzSprite/handleMouse_CLICK()[C:\Documents and Settings\hqm
\Local
Settings\Temp\lzswf9\lzgen59453\LzSprite.as:177]
I don't know what it means, but maybe I can figure out how to
attach to
the debug player in Firefox so I can set breakpoints, etc. I
don't know how to do that, or if that is possible. But it is a little
alarming that this error happens in the player in the browser but
not from the command line / standlone debugger.
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
