Home/ Questions/Q 831489
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T04:12:45+00:00

I’ve got an Adobe Flash 10 program that freezes in certain cases, however only

  • 0

I’ve got an Adobe Flash 10 program that freezes in certain cases, however only when running under a release version of the flash player. With the debug version, the application works fine.

What are the best approaches to debugging such issues? I considered installing the release player on my computer and trying to set some kind of non-graphical method of output up (I guess there’s some way to write a log file or similar?), however I see no way to have both the release and debug versions installed anyway 🙁 .

EDIT: Ok I managed to replace my version of flash player with the release version, and no freeze…so what I know so far is:

Flash:     Debug   Release
Vista 32:  works   works
XP PRO 32: works*  freeze
  • I gave them the debug players I had to test this

Hmm, seeming less and less like an error in my code and more like a bug in the player (10.0.45.2 in all cases)… At the very least id like to see the callstack at the point it freezes. Is there some way to do that without requiring them to install various bits and pieces, e.g. by letting flash write out a log.txt or something with a “trace” like function I can insert in the code in question?

EDIT2: I just gave the swf to another person with XP 32bit, same results 🙁

EDIT3:
Ok, through extensive use of flash.external.ExternalInterface.call(“alert”, “…”); I managed to find the exact line causing the problem (I also improved exception handling code so rather than freeze it told me there was an “unhandled” exception). The problem now is what on earth is flashes problem with this with the release player on some machines…

particles.push(p);

Which causes a TypeError #1034 on said platforms. Particles is a Vector.<Particle>, p is a Particle. I tested with getQualifiedClassName and got:

getQualifiedClassName(p) = ::Particle
getQualifiedClassName(particles) = __AS3__.vec::Vector.<::Particle>

Any ideas why this is a problem and what to do to make it work?

EDIT4:

Ok I seem to have solved this. The Particle class is just a simple internal class located after the package {…} in the action script file using it. I moved this into its own file (particle.as) and made it a proper public class in my package, and problem solved.

Maybe its a flash bug or maybe I missed the memo about not using internal classes in vectors or something, although if that’s the case I would have expected something or other (either at compile time or with debug runtimes) to disallow it explicitly, e.g. some error on the “private var particles:Vector.<Particle>;” line. If I get a chance I guess I’ll take a look at contacting the Adobe flash team concerning this or something.

Thanks for help giving debugging tips which I guess is more along the original questions lines 🙂

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Judging by when the freeze occurs, try to pinpoint some possibilities for what the offending code may be, and use De MonsterDebugger to check variables etc.

    EDIT:
    I’m pretty certain that the actual call stack is only available to you in the debug versions of the Flash Player / AIR. Still, it may be useful in the debug player to trace the stack from within the handler for the button to see if anything is out of place:

    var err:Error = new Error(“An Error”);
trace(err.getStackTrace());

    FYI the getStackTrace method is only available in the debug player, so there is no way to write it to a log.txt in production.

    • 0