Debugger Fails Depending On Source Code

[Guest]

Hi all,

I'm developing a largish Flash application using CS3 and AS3 (~1000 lines of code, multiple .fla files). Recently, the debugger stopped working normally, having been fine for the first few weeks of the project.

After selecting 'Debug Movie' in CS3, the view switches to the 'Debug: mygame.swf' pane and the message 'Attemping to launch and connect to Player using URL C:\dev\mygame\publish\mygame.swf' is shown in the output window. The code window displays the single line 'stop();' and the debugging options are disabled. No Flash Player window is ever seen.

After some investigation, I narrowed the problem down to a couple of .as files. Commenting out particular lines of code in these files caused the debugger to start working as normal. However, it doesn't appear to be the code itself as replacing this code with very simple statements such as 'var i : int = 0;' causes the debugger to fail again. Adding lines in other .as files does not appear to affect the debuggers behaviour.

Has anyone seen anything similar? One possibility is that I am hitting some kind of internal limit to the number of lines of code or variables that the debugger can deal with. Does that sound likely?

Many thanks in advance for any advice,

Dan

[Guest]

After a few more hours I've chanced across a workaround. If I run a different .fla (from the same project) in debug mode, it runs. Then run the proper .fla and it fails, as before. Then run it again and it succeeds.

Not ideal but at least I can debug again. This just makes it feel even more like a bug in the debugger.

As a bit of a newbie to the forum, would anyone be kind enough to point me towards a way of reporting these things to Adobe?

Still very interested in hearing of any similar experiences.

Dan