Eclipse: JVM Terminated. Exit Code=-1
Recently, for unknown reasons, starting up Eclipse gave me a nasty screen of errors, starting with:
JVM Terminated. Exit Code=-1
I've been using Eclipse and FDT for years, and this was the first time I've seen that so was stumped for a bit. Doing a search, gave numerous people running into similar problems, but frequently the error code was different, I'm not sure if "Exit Code =1" is a legitamate error or search engine indexing '-1' as '1'
What did work initially was removing the eclipse.ini, but then there wasn't enough memory being allocated for FDT (eclipse.ini has optional arguments '-Xmx' to tell the Java Runtime how much memory to save
Digging it turns
-vmargs was able to turn on/off the error. But then FDT wouldn't have enough memory to run 
Having had the Java runtime recently upgrade itself to 1.6, thought that was most of it. In the end, along with some other nasty issues (Explorer.exe taking 50% of the CPU and taking down any process)...I just ended up reinstalling Windows....joy.
It's working now, it turns out that the first param needs to be in front of the others, and I've had stability issues when the value is high (e.g. MaxPermSize=512M). Even though I have 3GB Ram, something between the JVM and Windows doesn't like it.
-XX:MaxPermSize=256M
-vmargs
-Xms40m
-Xmx768m
Flash: Local Connection Woes and Workarounds
LocalConnection is a pain in the but, been using it on a Desktop application, and so many hurdles.
Error #2044: Unhandled StatusEvent:. level=error, code=
Solution: From Zack at the awesome crew creative. "The unhandled Status error on localConnection is coming from a failed "send()" when the client is not recieving. You need to add a listener for a StatusEvent. try catch won't do it because the error is asynchronous.)". Thanks Zack!
Error #2044: Unhandled ErrorEvent Security localConnection (search)
Solution: use lc.allowDomain("*") or lc.allowDomain("localhost") in testing. How to specify meaningful domains when running locally don't quite make sense to me yet.
ArgumentError: Error #2082: Connect failed because the object is already connected. (search)
Solution: use try catch around the lc.connect attempt.
Troyworks AS3.0 framework on Google Code
A pre-beta version of the codebase has been checked in to googlecode. While some core parts are solid, there are still some major refactorings planned which I'm working hard on. Please follow this instructions here to check things out, and ping me if you are interested in contributing to the MIT licensed project.
http://code.google.com/p/troyworks/source/checkout