Skip to content
June 23, 2010 / edeustace

Can’t debug your flash application in Firefox 3.6.4 – disable the new hang detector

In the middle of a debug session, my Firefox got upgraded to 3.6.4. All of a sudden I kept getting “The flash player has crashed…”. This is because Firefox comes with a new hang detector.

To disable it:
1. Launch Firefox and go to about:config
2. Search for dom.ipc.plugins.timeoutSecs
3. Set the value to -1 (for infinite timeout).

And you’re done and debugging again.

I’m guessing the same will apply for firebug debug sessions too.

More info here.

Advertisements

5 Comments

Leave a Comment
  1. eclps / Jun 23 2010 10:46 pm

    This fix does not actually solve the problem. If you’re using a debug flash player and it throws an exception firefox will simply lockup and become unusable. The exception window will show up now (as opposed to the dead plugin icon) however you cannot click on continue as their plugin “sandbox”, plugin-container.exe, is also not responding. If you terminate the plugin-container it simply reverts back to the dead plugin icon. Mozilla dropped the ball on this one…

    • edeustace / Jun 24 2010 7:31 am

      Thanks for the info. Haven’t had an exception thrown yet. Is there a bugzilla on this?
      Best,
      Ed

    • edeustace / Jun 24 2010 7:45 am

      Hi,
      I just tried this with a simple app and I couldn’t reproduce what you described. Once I clicked “continue” in the exception window I was able to carry on debugging.
      Here’s the app:

      <?xml version="1.0" encoding="utf-8"?>
      <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
      	xmlns:s="library://ns.adobe.com/flex/spark" 
      	xmlns:mx="library://ns.adobe.com/flex/mx"
      	creationComplete="windowedapplication1_creationCompleteHandler(event)">
      	<fx:Script>
      		<![CDATA[
      			import flash.utils.setTimeout;
      			import mx.events.FlexEvent;
      			
      			protected function windowedapplication1_creationCompleteHandler(event:FlexEvent):void
      			{
      				setTimeout( function() : void { throw new Error( "i'm an error" );}, 2000 );
      			}
      			
      		]]>
      	</fx:Script>
      	<s:Label fontSize="28" text="This app throws an error"/>
      </s:Application>
      

      Do you have a sample that recreates the issue for you?
      Ed

  2. arvind / Jun 30 2010 4:53 am

    Facing the same problem as eclps

  3. Jonathan / Jul 13 2010 2:40 pm

    Got a similar problem, I always use firefox to debug when building with flex builder, if I hit a bad piece of code or an infinite loop and I close the browser I still have these processes running in the background eating up an unbelievable amount of resources, was pulling out my hair trying to figure out why my computer was hurting so bad,

    thanks for the info!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: