Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

UncaughtErrorEvent - Adobe ActionScript® 3 (AS3 ) API Reference

Explorer ,
Jan 11, 2013 Jan 11, 2013
TOPICS
ActionScript
554
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 11, 2013 Jan 11, 2013

How I can get the stack trace In a non-debugger version of the runtime (Flash Player 11.4 or earlier and AIR 1.4 or earlier)?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 11, 2013 Jan 11, 2013

Without using a debugger you could use something like Adobe Scout to profile the SWF:

http://gaming.adobe.com/technologies/scout/

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 31, 2013 Jan 31, 2013

I presume David_Great is talking about logging uncaught errors when the application is running on a users/clients non-debugger version of Flash/Air.

That is what I am currently looking for. Anyone any info on that?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 31, 2013 Jan 31, 2013
LATEST

To my knowledge, Scout (as I used it in beta) ran on any SWF currently playing. You didn't need any special version of a plugin installed. It would help if you had telemetry enabled on the SWF, but not necessary. I was able to take a lot of old SWFs and run it through Scout while gaining interesting information.

Just remember Scout is not a debugger to the point it captures 100% of everything. You set the millisecond interval and it does a pretty good job, but you're capturing a series of 'snapshots'. That means at any one time your snapshot could be out of order or delayed. Especially when capturing very expensive features like Stage3D (what I did with it). I ran my SWF in a browser online and Scout found the SWF and started immediately profiling it. Though I noticed the millisecond rate I chose affected the heaps I saw.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines