Usually when this happens an uncaught error (usually do to something asynchronous not using the Async API, an asynchronous race condition or an asynchronous error) is getting thrown outside of the FlexUnit framework.
What version of FlexUnit are you using currently? If you are using the 4.1 release candidate 2, you add an uncaughtErrorHandler.
While FlexUnit can't recover gracefully from this error, it will at least stop the possibility of hanging and help you understand where the issue may exist.
In your runner, the uncaught error handler is added to the core, passing it the loaderInfo
core = new FlexUnitCore();
core.addUncaughtErrorListener( systemManager.loaderInfo ); //or any valid reference to the loaderInfo
core.addListener( CIListener );
core.run( SimpleTest );This would be my first/best suggestion for you. If it yields more information, we can work our way backward to find the actual root cause.If it doesn't help, we can also try more things. One more issue, the 4,1 rc2 candidate shortens the stack depth considerably from previous versions. If you aren't yet running that version, it may be worth it just for that dianostic alone.Mike
Thanks, Mike we do have more than a couple errors popping up when we run the tests using the flash debugger and we are working on fixing those. We are currently using Flexunit 4.0 stable but I'll see if we can try out 4.1 rc2 and try out the uncaughtErrorHandler and let you know what we find.
Thanks again for your quick response!