This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox freezes and then closes

  • 7 replies
  • 1 has this problem
  • 8 views
  • Last reply by Shadow110

more options

The main problem I'm having is Firefox freezes and then closes. I look at the task manager and there are still Firefox processes running but they disappear after a minute each. It's been happening for a couple of months now, and sometimes it can take a week or a matter of hours.

Something that might be related to this is a problem with tabs where, after opening, the tab contents will only show a throbber and never display the contents of the page.

Some possibly helpful information from the console are the following messages which accompany every crash: IPDL protocol error: could not lookup id for PTexture IPDL protocol error: Error deserializing 'textureParent' (PTexture) member of 'TimedTexture'

Well before the crash I'll also see (many times):

      1. !!! [Parent][DispatchAsyncMessage] Error: PClientSourceOp::Msg___delete__ Route error: message sent to unknown actor ID
The main problem I'm having is Firefox freezes and then closes. I look at the task manager and there are still Firefox processes running but they disappear after a minute each. It's been happening for a couple of months now, and sometimes it can take a week or a matter of hours. Something that might be related to this is a problem with tabs where, after opening, the tab contents will only show a throbber and never display the contents of the page. Some possibly helpful information from the console are the following messages which accompany every crash: IPDL protocol error: could not lookup id for PTexture IPDL protocol error: Error deserializing 'textureParent' (PTexture) member of 'TimedTexture' Well before the crash I'll also see (many times): ###!!! [Parent][DispatchAsyncMessage] Error: PClientSourceOp::Msg___delete__ Route error: message sent to unknown actor ID

All Replies (7)

more options

Sorry about that, re OS and no about : crashes

Modified by Shadow110

more options

about:crashes does not exist for me.

more options

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?


Start your Computer in safe mode with network support. Then start Firefox. Try Secure websites. Is the problem still there?

http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting Any Computer In Safe Mode; Free Online Encyclopedia


How to crash Firefox (All Systems); Instructions here; https://developer.mozilla.org/en-US/docs/Mozilla/How_to_report_a_hung_Firefox

This link has a program that can crash Firefox.

more options

If it didn't take so long to reproduce, then I would run in safe mode, but FF is the only browser I use. If it would really really help, then I might do that. I'm hoping someone might be familiar with where those errors are coming from and what they could mean. I also want to record this problem in case someone else does.

FreeBSD doesn't really have a safemode per se. (It has something called safe mode but it's dated.)

I'll see about crashing the Firefox processes next time.

more options

Bug 1410187 not sure is or not but was not present since 58. Not sure what to do about this.

Have you tried a reinstall ?

more options

I just upgraded the package and I'm directing stdin and err to a log. I can look into other ways to collect information. It could take a couple of days until it hangs again. I will certainly report back more helpful information when I have it.

more options

I know not where things may be in your version. This for Windows if you can figure this out great : To be Checked and turned off unless needed for accessibility : Please : go to the Firefox 3 Bar Menu --> Options --> Privacy & Security panel and under Permissions check (put a tick in the box) the setting to Prevent Accessibility Services from accessing your browser.

Multi-Processor Support : Go to the 3 Bar Menu then Options --> General --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 1 = No Multiprocessor = slow again. Try 2 Restart Firefox after making these changes please. Note : Hardware Acceleration is for Video Card, Monitor to see if remain off or to turn back on.