A technique, which worked for me in the past, is to reduce the code as
much as possible.
Cheers
Ralf.
On Dec 1, 2007 10:10 PM, Mike Krotscheck [EMAIL PROTECTED] wrote:
I am currently trying to debug an intermittent bug within our application
that causes a browser crash. Not just a hey, the application threw a
runtime error, I mean a do-not-pass-go, do-not-output-useful-debug-stack,
do-not-write-useful-info-to-log, .ocx illegal exception that kills the
browser.
So my question is: What methods have you guys used to track these things
down? I've gone the massive trace statement route, but that's proven less
than helpful.
Assume FB3, compiling to 2.0.1, IE FF testing on player versions r28, r45,
r47 and r60. IE gives some slightly useful information: Unhandled exception
at 0x3006c907 in iexplore.exe: 0xC005: Access violation reading location
0x.
Under other circumstances I'd say it's an out-of-memory error since we've
seen those before, but the application has since been scrubbed and optimized
and profiled to death, and doesn't suck up more than 35 megs on a bad day.
Michael Krotscheck
Senior Developer
RESOURCE INTERACTIVE
www.resource.com
[EMAIL PROTECTED]
This email and any of its attachments may contain Resource Interactive
proprietary information, which is privileged, confidential and may be
subject to copyright or other intellectual property rights belonging to
Resource Interactive. This email is intended solely for the use of the
individual or entity to which it is addressed. If you are not the intended
recipient of this email, you are hereby notified that any dissemination,
distribution, copying or action taken in relation to the contents of and
attachments to this email is strictly prohibited and may be unlawful. If you
have received this email in error, please notify the sender immediately and
permanently delete the original and any copy of this email and any printout.
--
Ralf Bokelberg [EMAIL PROTECTED]
Flex Flash Consultant based in Cologne/Germany
