Skip to main content
February 8, 2011
Question

Previously working program compiles then does nothing.

  • February 8, 2011
  • 2 replies
  • 1287 views

I've been working on this project for over a year and a week ago, it just stopped working.  It compiles without errors.  It launches the AIR window with all the correct dimensions et. al.,  That window however is empty.  No trace statements run, not even the first trace as the first statement in the code block in the constructor of the base class.  It seems as though it never even reaches there.  No amount of deleting ASO files, resigning, running in the debugger, adding breakpoints, etc does any good.  In the debugger, it's as though execution is halted before the debugger produces any output (I don't really use the debugger, so this may be my ignorance).  There's no output after the swf size report line in the output window and nothing in the compiler errors window.   Nothing.

I suspect a corruption in some element from the library, but I'm not even certain why now that I think that.

Sorry this is so vague.... I've been beating my head against a wall for a week when results are expected by my supervisors, and I'm just absolutely out of ideas.

This topic has been closed for replies.

2 replies

Participant
March 3, 2011

I am also having the same frustrating issue... I have an Air 2.0 app in the marketplace currently. I've made some change to the app and went to go compile it. It compiles with no errors, but when it runs it, cycles through the 4 keyframes on the main time line, ignoring any stop() or actionscript.  (similar to how it would act if there were compiler errors, but there is nothing in the output window.)

If I comment out all the code that refers to importing and using the LicenseManager, the air app will compile and and run perfectly.

I can compile and run the test LicenceManager fine. (the original app used the LicenseManager just fine), using all the same settings and source/library paths of my app.

I verified that I am using the correct license.swc (for air 2.0).

But anytime I just to use the LicenseManager in my app, the compiler will not give any errors, and the app just flashes between the keyframes.

Would love some advice on how to figure out what is causing the issue.

Keith

Participant
March 3, 2011

I should mention I am using Flash CS5 Profession on a Windows 7 64bit machine. Also tried compiling it

on a Windows XP (CS5) machine with same results.


March 3, 2011

Well the solution for me was increasing the java heap size via environment variables (still possible that one library item was also causing trouble, but it seems less likely and would have been a contributor, not the cause). I've been golden ever since.

Have you tried increasing yours and seeing if it made any difference?

It seems like our problems might be unrelated if you actually have frames running.  In mine, execution halted as soon as the native app/window container was drawn due to the java engine failing right at that point.   Dunno.  Wish I could be more help.

chris.campbell
Legend
February 8, 2011

Hmm, this sounds odd.  No changed occured with your project before it broke?  Does this occur with both a release/installed build and when running from the IDE?  Did you recently upgrade the SDK or Runtime?  What OS are you running, and have you tried this on more than one machine?  Finally, any chance you could export the project and email it to me so I could try taking a look?  Feel free to contact me at ccampbel@adobe.com.

Thanks,

Chris

February 9, 2011

No.  No change.  I'm running Flash CS5 on WinXp64 on an iMac.  It also fails from CS5 on my pitiful Dell Inspiron 1520 running Win 7 Enterprise.

What do you mean by export?    It's rather large all told.

February 10, 2011

I've got it working again by starting with a new flash(air) file.   I commented out a dozen classes that had library dependencies and bit by bit, copied bits from the old file's library to the new file to satisfy dependencies and compiled each time, and I'm now back to about a third of my classes being in, with dependencies, and all is working. (It's compiling faster too.... *sigh*  I don't look forward to returning to 5 minute compile times when all my classes and library stuffies are back.  I'm being spoiled right now.)

Waiting to see what, if anything, kills it.

I replaced the application update framework files with those from the most recent AIR SDK release, as I suspected that might be part of the problem.  So far that's all working well too.