X
Tap here to go to the mobile version of the site.

Support Forum

Daily Crash Reports Continued...

Posted

Did Firefox Support Forum go back to its previous version within the last few hours, or did it just happen to me? This can be deleted once I get an answer, but I'm asking, because I had a long-running thread on the other forum and need to know if I need to repost my problem I was working on. For instance, this was my most recent crash:

bp-912166d8-b038-40e3-8f8a-9b8860170419

Did Firefox Support Forum go back to its previous version within the last few hours, or did it just happen to me? This can be deleted once I get an answer, but I'm asking, because I had a long-running thread on the other forum and need to know if I need to repost my problem I was working on. For instance, this was my most recent crash: bp-912166d8-b038-40e3-8f8a-9b8860170419

Modified by FireFoxFan1

Additional System Details

Installed Plug-ins

Three, but all permanently disabled.

Application

  • Firefox 52.0.2
  • User Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0
  • Support URL: https://support.mozilla.org/1/firefox/52.0.2/WINNT/en-US/

Extensions

  • Application Update Service Helper 2.0 (aushelper@mozilla.org)
  • Multi-process staged rollout 1.12 (e10srollout@mozilla.org)
  • Pocket 1.0.5 (firefox@getpocket.com)
  • Site Deployment Checker 1.0 (deployment-checker@mozilla.org)
  • Web Compat 1.0 (webcompat@mozilla.org)
  • Status-4-Evar 2016.10.11.01 (status4evar@caligonstudios.com) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: Intel(R) HD Graphics
  • adapterDescription2:
  • adapterDeviceID: 0x0046
  • adapterDeviceID2:
  • adapterDrivers: igdumdx32 igd10umd32
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterSubsysID: 04101028
  • adapterSubsysID2:
  • adapterVendorID: 0x8086
  • adapterVendorID2:
  • crashGuards: [{u'prefName': u'gfx.crash-guard.status.d3d9video', u'type': u'd3d9video'}]
  • currentAudioBackend: wasapi
  • direct2DEnabled: False
  • direct2DEnabledMessage: [u'']
  • directWriteEnabled: True
  • directWriteVersion: 6.2.9200.22084
  • driverDate: 1-30-2013
  • driverDate2:
  • driverVersion: 8.15.10.2993
  • driverVersion2:
  • featureLog: {u'fallbacks': [], u'features': [{u'status': u'disabled', u'description': u'Compositing', u'name': u'HW_COMPOSITING', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'disabled', u'message': u'Disabled by pref', u'type': u'user'}]}, {u'status': u'unavailable', u'description': u'Direct3D11 Compositing', u'name': u'D3D11_COMPOSITING', u'log': [{u'status': u'unavailable', u'message': u'Hardware compositing is disabled', u'type': u'default'}]}, {u'status': u'unavailable', u'description': u'Direct3D9 Compositing', u'name': u'D3D9_COMPOSITING', u'log': [{u'status': u'unavailable', u'message': u'Hardware compositing is disabled', u'type': u'default'}]}, {u'status': u'unavailable', u'description': u'Direct2D', u'name': u'DIRECT2D', u'log': [{u'status': u'unavailable', u'message': u'Direct2D requires Direct3D 11 compositing', u'type': u'default'}]}, {u'status': u'disabled', u'description': u'Direct3D11 hardware ANGLE', u'name': u'D3D11_HW_ANGLE', u'log': [{u'status': u'unavailable', u'message': u'D3D11 compositing is disabled', u'type': u'default'}, {u'status': u'disabled', u'message': u'D3D11 compositing is disabled', u'type': u'env'}]}]}
  • info: {u'ApzWheelInput': 1, u'ApzTouchInput': 1, u'AzureFallbackCanvasBackend': u'cairo', u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'skia', u'AzureContentBackend': u'skia'}
  • isGPU2Active: False
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'']
  • numTotalWindows: 1
  • supportsHardwareH264: No; Hardware video decoding disabled or blacklisted
  • webgl2Renderer: WebGL creation failed: * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Exhausted GL driver caps.
  • webglRenderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D9Ex vs_3_0 ps_3_0)
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Basic

Modified Preferences

Misc

  • User JS: No
  • Accessibility: No
cor-el
  • Top 10 Contributor
  • Moderator
17540 solutions 158604 answers

Helpful Reply

Yes, you are correct the forum did revert to make it possible to look into some issues with the new forum. See: https://support.mozilla.org/en-US/forums/contributors/712410

Yes, you are correct the forum did revert to make it possible to look into some issues with the new forum. See: https://support.mozilla.org/en-US/forums/contributors/712410

Question owner

So this is only happening for a day? Will the post I was working on with you and John still be there, or is it gone? I need to know this as we were getting fairly close.

BTW, is the crash report I posted the same as my other ones?

So this is only happening for a day? Will the post I was working on with you and John still be there, or is it gone? I need to know this as we were getting fairly close. BTW, is the crash report I posted the same as my other ones?

Modified by FireFoxFan1

cor-el
  • Top 10 Contributor
  • Moderator
17540 solutions 158604 answers

It is not known how long this change will last, but I do not think that it is for one day. They need to do some testing (knowledge base redirects) and possibly other things need to be looked into as well. You can keep an eye on the contributors forum thread I posted above if you are interested.

The crash report looks the same to me, but I do not have links to your older reports at hand. It looks still like a problem with multi-process windows to me.

The crash report would indicate that multi-process is disabled by add-ons (AddonsShouldHaveBlockedE10s).

  • Firefox 52.0.2 Crash Report [@ IPCError-browser | ShutDownKill ]

What is the current value of the multi-process windows prefs?

  • browser.tabs.remote.autostart = false
  • browser.tabs.remote.autostart.2 = false

How are you closing Firefox?

Use one of these to close Firefox if you are currently doing that by clicking the close X on the Firefox title bar.

  • "3-bar" menu button# -> Exit (Power button)
  • Windows: File -> Exit
  • Mac: Firefox -> Quit Firefox
  • Linux: File -> Quit
It is not known how long this change will last, but I do not think that it is for one day. They need to do some testing (knowledge base redirects) and possibly other things need to be looked into as well. You can keep an eye on the contributors forum thread I posted above if you are interested. The crash report looks the same to me, but I do not have links to your older reports at hand. It looks still like a problem with multi-process windows to me. The crash report would indicate that multi-process is disabled by add-ons (AddonsShouldHaveBlockedE10s). *Firefox 52.0.2 Crash Report [@ IPCError-browser | ShutDownKill ] What is the current value of the multi-process windows prefs? *browser.tabs.remote.autostart = false *browser.tabs.remote.autostart.2 = false How are you closing Firefox? Use one of these to close Firefox if you are currently doing that by clicking the close X on the Firefox title bar. *"3-bar" menu button# -> Exit (Power button) *Windows: File -> Exit *Mac: Firefox -> Quit Firefox *Linux: File -> Quit
John99 971 solutions 13138 answers

Who knows whether it will be a couple of days or a couple of months. I for one would be happy with a couple of months as that would give us a better chance of getting some of the known issues with the forum software fixed and tested properly before we start using the software again.

It would have been much better if we had had at least a week or twos notice of the rollback and had what was the new forum software available in a read only form. (In fact we probably do have that but not sure who will get access to it)

Who knows whether it will be a couple of days or a couple of months. I for one would be happy with a couple of months as that would give us a better chance of getting some of the known issues with the forum software fixed and tested properly before we start using the software again. It would have been much better if we had had at least a week or twos notice of the rollback and had what was the new forum software available in a read only form. (In fact we probably do have that but not sure who will get access to it)
John99 971 solutions 13138 answers

I've just been given notes about read only access to the Lithium read only info, but have not tried them out yet.

I've just been given notes about read only access to the Lithium read only info, but have not tried them out yet.
John99 971 solutions 13138 answers

cor-el Info has been available from Kitsune Mods forum for a few hours it has just been pointed out to me.

cor-el Info has been available from Kitsune Mods forum for a few hours it has just been pointed out to me.
cor-el
  • Top 10 Contributor
  • Moderator
17540 solutions 158604 answers

Thanks John

Thanks John

Question owner

cor-el said

The crash report looks the same to me, but I do not have links to your older reports at hand. It looks still like a problem with multi-process windows to me. The crash report would indicate that multi-process is disabled by add-ons (AddonsShouldHaveBlockedE10s).
  • Firefox 52.0.2 Crash Report [@ IPCError-browser | ShutDownKill ]
What is the current value of the multi-process windows prefs?
  • browser.tabs.remote.autostart = false
  • browser.tabs.remote.autostart.2 = false
How are you closing Firefox? Use one of these to close Firefox if you are currently doing that by clicking the close X on the Firefox title bar.
  • "3-bar" menu button# -> Exit (Power button)
  • Windows: File -> Exit
  • Mac: Firefox -> Quit Firefox
  • Linux: File -> Quit

browser.tabs.remote.autostart.2 is set to "true."

Anyway, just updated to the newest version and it's hanging like crazy, which makes all of the work we did before seemingly pointless.

BTW, is that long-running thread we worked on still available or will we have to start back from the beginning?

''cor-el [[#answer-960838|said]]'' <blockquote> The crash report looks the same to me, but I do not have links to your older reports at hand. It looks still like a problem with multi-process windows to me. The crash report would indicate that multi-process is disabled by add-ons (AddonsShouldHaveBlockedE10s). *Firefox 52.0.2 Crash Report [@ IPCError-browser | ShutDownKill ] What is the current value of the multi-process windows prefs? *browser.tabs.remote.autostart = false *browser.tabs.remote.autostart.2 = false How are you closing Firefox? Use one of these to close Firefox if you are currently doing that by clicking the close X on the Firefox title bar. *"3-bar" menu button# -> Exit (Power button) *Windows: File -> Exit *Mac: Firefox -> Quit Firefox *Linux: File -> Quit </blockquote> browser.tabs.remote.autostart.2 is set to "true." Anyway, just updated to the newest version and it's hanging like crazy, which makes all of the work we did before seemingly pointless. BTW, is that long-running thread we worked on still available or will we have to start back from the beginning?
John99 971 solutions 13138 answers

Sorry FireFoxFan1 it is all very chaotic at present.

It's turning out as more of a firefighting situation than a carefully orchestrated and planned rollback. It may be early next week before we can give good answers. I am sure your old thread is not lost and will be retained. cor-el or myself may gain access to it later today

Sorry FireFoxFan1 it is all very chaotic at present. It's turning out as more of a firefighting situation than a carefully orchestrated and planned rollback. It may be early next week before we can give good answers. I am sure your old thread is not lost and will be retained. cor-el or myself may gain access to it later today

Question owner

Okay, so my crash report right now looks like all my other ones:

bp-b201d8ec-774b-4841-9aca-cc2220170421

So, I'm kind of thinking having gone through turning on and off multiprocess and hardware acceleration and the same crash reports happening that it may be a profile issue. It must be a specific setting, though, because this eventually happens with any new profile I make.

I've been told in the past it might have something to do with my privacy settings. At the moment I have my "History" settings marked as "Use custome settings for history" with "accept cookies from sites" checked and marked as "always" and then kept until "I close Firefox". Then I have "Clear history when Firefox closes" checked, which I was told way back in earlier version has caused problems.

Would any of these settings explain this crash? If I'm getting almost identical crashes, this would seem fairly easy to throw out what it's not.

Okay, so my crash report right now looks like all my other ones: bp-b201d8ec-774b-4841-9aca-cc2220170421 So, I'm kind of thinking having gone through turning on and off multiprocess and hardware acceleration and the same crash reports happening that it may be a profile issue. It must be a specific setting, though, because this eventually happens with any new profile I make. I've been told in the past it might have something to do with my privacy settings. At the moment I have my "History" settings marked as "Use custome settings for history" with "accept cookies from sites" checked and marked as "always" and then kept until "I close Firefox". Then I have "Clear history when Firefox closes" checked, which I was told way back in earlier version has caused problems. Would any of these settings explain this crash? If I'm getting almost identical crashes, this would seem fairly easy to throw out what it's ''not.''

Question owner

-Someone can change the title to "Continued Crashes" or some such thing-

Another day, another crash report:

bp-6b95a74b-3abc-4653-bd63-3849c0170422

This time I expiremented with turning off my Microsoft Security Essentials anti-virus program. So, now we can rule out my suspicion that it was that. We can also rule out extensions and add-ons since they are now always disabled.

-Someone can change the title to "Continued Crashes" or some such thing- Another day, another crash report: bp-6b95a74b-3abc-4653-bd63-3849c0170422 This time I expiremented with turning off my Microsoft Security Essentials anti-virus program. So, now we can rule out my suspicion that it was that. We can also rule out extensions and add-ons since they are now always disabled.

Modified by FireFoxFan1

cor-el
  • Top 10 Contributor
  • Moderator
17540 solutions 158604 answers

You can edit the first (question) post to be able to change the title.

You can edit the first (question) post to be able to change the title.
John99 971 solutions 13138 answers

The text of recent posts in Lithium the other forum software:


You do appear to be making progress. I think what you need to do is explore the apparently fully working configurations of Firefox and figure out what they are. Something I have been trying to help you identify for a while. Then just change one factor at a time to see what then happens.

   FireFoxFan1 wrote:
   Turned on hardware acceleration and turned off multi-process.  Firefox totally froze after an hour or so.  Like you said, there was no crash report.  The problem is that this was a complete freeze of the browser and I had to go into task manager to close it out.


   So to reiterate, I either get crashes I can manually close out the browser from using the menu bar, or I get total freezes which I have to close down using the task manager.  It seems this most recent one was the result of turning off multi-process.


Do not forget you do have options to configure Firefox so it works.

You may have

   Profile issues
   Those will go away in a new profile.
   You may be able to recreate them by using problem profiles.
   Windows Issues
   Those go away in Windows own Safe Mode

Some or all of your issues may be a combination of those two issues.


   Either way, it makes for an inconsistent Firefox session.  Personally, I'm still suspicious of my malware protection and anti-virus programs as the possible source of this.  But since you've not mentioned them, I wouldn't know what to offer you.

I would imagine that in Windows Safe mode any Security software is effectively disabled. It seems your install of Firefox works trouble-free in Windows Safe Mode so it may be worth testing Firefox with the Security software temporarily removed but not in Windows safe mode. If that works ok it is suggests that your suspicions about the Security software are well founded. Note that trying to test with security software disabled rather than temporarily removed could in some instances be problematic. I believe in some cases security software may not be fully disabled unless you do temporarily remove it.


   Anyway, I just turned hardware acceleration back off and turned multi-process back on.


Which you seem to know & expect causes your Firefox to crash. So later on we still need to explore what happens with multiprocess turned off, and also what happens with Hardware acceleration on - that may need drivers updating for instance.



Turned on hardware acceleration and turned off multi-process. Firefox totally froze after an hour or so. Like you said, there was no crash report. The problem is that this was a complete freeze of the browser and I had to go into task manager to close it out.


So to reiterate, I either get crashes I can manually close out the browser from using the menu bar, or I get total freezes which I have to close down using the task manager. It seems this most recent one was the result of turning off multi-process.


Either way, it makes for an inconsistent Firefox session. Personally, I'm still suspicious of my malware protection and anti-virus programs as the possible source of this. But since you've not mentioned them, I wouldn't know what to offer you.


Anyway, I just turned hardware acceleration back off and turned multi-process back on.



Thanks for the clarification.

I think the Windows Safe mode aspect of this issue is very important.

   FireFoxFan1 wrote:
   What I tried was windows safe mode, firefox safe mode, all add-ons disabled and a clean profile.  That is the only one that has gotten no errors.  I've also tried all of that minus being in windows safe mode and got errors. 

So and this is important.

If you use Firefox outside of Windows safe mode you mostly get problems ?

but you have already said you do not yet see problems in Windows safe mode.

If so it is a strongly Windows related fault.

Maybe related to driver software or security software for instance.


Turning off hardware acceleration is by no means a cure all solution.

   I always have hardware acceleration off, because it's always been one of the first things moderators have told us when we've had problems. 

Hardware acceleration can sometimes cause issues, but It can also help with Firefox and speed things up. It Is not normal to leave hardware acceleration off but is sometimes necessary. Especially if a user reports Firefox works better with it turned off, but I do not know whether or not that is the case for you and your install of Firefox with your particular hardware and graphics drivers.


   As for multi-process, I've explained a dozen times now that I've noticed no difference in peformance, positively, as it relates to crashes.  They still happen and on top of that, turning of multi-process makes the browser crawl so it's the worst of both worlds.
 Multi process mode is hopefully faster, which you seem to agree happens. However:
   You may not have noticed how it relates to crashes but I am pretty certain you will not get the current series of crash IDs if you turn off the multiprocess mode. It may prevent crashes if you turn this off. It will almost certainly stop all crashes with the current Crash Signature  (Signature: IPCError-browser | ShutDownKill)
   Although I can not guarantee you will not still get crashes, but if the crash signature changes it may then be more informative.
   If the browser crawls we can investigate that, although to be honest it is easier usually to look at crashes.
   I have no interest in trying to troubleshoot issues in Multi Process Firefox. Certainly not in cases where single process Firefox already has issues. Others may help but I do not have the knowledge to do so; or the inclination at present; to learn more about multiprocess Firefox, whilst it is mainly experimental or at least avoidable.



What I tried was windows safe mode, firefox safe mode, all add-ons disabled and a clean profile. That is the only one that has gotten no errors. I've also tried all of that minus being in windows safe mode and got errors.


I always have hardware acceleration off, because it's always been one of the first things moderators have told us when we've had problems. As for multi-process, I've explained a dozen times now that I've noticed no difference in peformance, positively, as it relates to crashes. They still happen and on top of that, turning of multi-process makes the browser crawl so it's the worst of both worlds.

The text of recent posts in Lithium the other forum software: You do appear to be making progress. I think what you need to do is explore the apparently fully working configurations of Firefox and figure out what they are. Something I have been trying to help you identify for a while. Then just change one factor at a time to see what then happens. FireFoxFan1 wrote: Turned on hardware acceleration and turned off multi-process. Firefox totally froze after an hour or so. Like you said, there was no crash report. The problem is that this was a complete freeze of the browser and I had to go into task manager to close it out. So to reiterate, I either get crashes I can manually close out the browser from using the menu bar, or I get total freezes which I have to close down using the task manager. It seems this most recent one was the result of turning off multi-process. Do not forget you do have options to configure Firefox so it works. You may have Profile issues Those will go away in a new profile. You may be able to recreate them by using problem profiles. Windows Issues Those go away in Windows own Safe Mode Some or all of your issues may be a combination of those two issues. Either way, it makes for an inconsistent Firefox session. Personally, I'm still suspicious of my malware protection and anti-virus programs as the possible source of this. But since you've not mentioned them, I wouldn't know what to offer you. I would imagine that in Windows Safe mode any Security software is effectively disabled. It seems your install of Firefox works trouble-free in Windows Safe Mode so it may be worth testing Firefox with the Security software temporarily removed but not in Windows safe mode. If that works ok it is suggests that your suspicions about the Security software are well founded. Note that trying to test with security software disabled rather than temporarily removed could in some instances be problematic. I believe in some cases security software may not be fully disabled unless you do temporarily remove it. Anyway, I just turned hardware acceleration back off and turned multi-process back on. Which you seem to know & expect causes your Firefox to crash. So later on we still need to explore what happens with multiprocess turned off, and also what happens with Hardware acceleration on - that may need drivers updating for instance. ----------- Turned on hardware acceleration and turned off multi-process. Firefox totally froze after an hour or so. Like you said, there was no crash report. The problem is that this was a complete freeze of the browser and I had to go into task manager to close it out. So to reiterate, I either get crashes I can manually close out the browser from using the menu bar, or I get total freezes which I have to close down using the task manager. It seems this most recent one was the result of turning off multi-process. Either way, it makes for an inconsistent Firefox session. Personally, I'm still suspicious of my malware protection and anti-virus programs as the possible source of this. But since you've not mentioned them, I wouldn't know what to offer you. Anyway, I just turned hardware acceleration back off and turned multi-process back on. -------- Thanks for the clarification. I think the Windows Safe mode aspect of this issue is very important. FireFoxFan1 wrote: What I tried was windows safe mode, firefox safe mode, all add-ons disabled and a clean profile. That is the only one that has gotten no errors. I've also tried all of that minus being in windows safe mode and got errors. So and this is important. If you use Firefox outside of Windows safe mode you mostly get problems ? but you have already said you do not yet see problems in Windows safe mode. If so it is a strongly Windows related fault. Maybe related to driver software or security software for instance. Turning off hardware acceleration is by no means a cure all solution. I always have hardware acceleration off, because it's always been one of the first things moderators have told us when we've had problems. Hardware acceleration can sometimes cause issues, but It can also help with Firefox and speed things up. It Is not normal to leave hardware acceleration off but is sometimes necessary. Especially if a user reports Firefox works better with it turned off, but I do not know whether or not that is the case for you and your install of Firefox with your particular hardware and graphics drivers. As for multi-process, I've explained a dozen times now that I've noticed no difference in peformance, positively, as it relates to crashes. They still happen and on top of that, turning of multi-process makes the browser crawl so it's the worst of both worlds. Multi process mode is hopefully faster, which you seem to agree happens. However: You may not have noticed how it relates to crashes but I am pretty certain you will not get the current series of crash IDs if you turn off the multiprocess mode. It may prevent crashes if you turn this off. It will almost certainly stop all crashes with the current Crash Signature (Signature: IPCError-browser | ShutDownKill) Although I can not guarantee you will not still get crashes, but if the crash signature changes it may then be more informative. If the browser crawls we can investigate that, although to be honest it is easier usually to look at crashes. I have no interest in trying to troubleshoot issues in Multi Process Firefox. Certainly not in cases where single process Firefox already has issues. Others may help but I do not have the knowledge to do so; or the inclination at present; to learn more about multiprocess Firefox, whilst it is mainly experimental or at least avoidable. -------- What I tried was windows safe mode, firefox safe mode, all add-ons disabled and a clean profile. That is the only one that has gotten no errors. I've also tried all of that minus being in windows safe mode and got errors. I always have hardware acceleration off, because it's always been one of the first things moderators have told us when we've had problems. As for multi-process, I've explained a dozen times now that I've noticed no difference in peformance, positively, as it relates to crashes. They still happen and on top of that, turning of multi-process makes the browser crawl so it's the worst of both worlds.

Question owner

That was very difficult to read and seperate out what you were saying and what you were quoting from me. Perhaps it'd be best simply to quote me, and if you have to quote me inside a quote that's fine.

Anyway, if you think it's something with Windows, I imagine you guys have had enough of these hangs with multi-process to nail down at least what it isn't with suspicion of what it is. What is your idea since we've gone through all of this slowly ruling out what it isn't? I've told you which security program I have protecting my computer (Microsoft Security Essentials), which I think we ruled out since one of my replies here was how I had turned off protection and still got the same crashes. As for drivers, that's not something we've looked into, I don't think, so maybe that's the next route.

Anyway, I JUST had another one:

bp-f10452e1-dc50-482d-88a1-e56b80170424

And one from yesterday:

bp-28bd1cf9-f7e4-4f26-9b10-405a00170424

Lastly, I'm not interested in having to start new profiles again and again unless it's going to tell us what's wrong with the existing one I'm using. We've already been the new profile route, anyway. And, like I'd tried pushing, perhaps it's my browser security settings as I was told it might be in the past, but you've not once talked about how that might be the problem.

I want a single profile with my existing bookmarks. I've already made quite a few sacrifices to get this far such as deleting extensions and add-ons.

That was very difficult to read and seperate out what you were saying and what you were quoting from me. Perhaps it'd be best simply to quote me, and if you have to quote me inside a quote that's fine. Anyway, if you think it's something with Windows, I imagine you guys have had enough of these hangs with multi-process to nail down at least what it isn't with suspicion of what it is. What is your idea since we've gone through all of this slowly ruling out what it isn't? I've told you which security program I have protecting my computer (Microsoft Security Essentials), which I think we ruled out since one of my replies here was how I had turned off protection and still got the same crashes. As for drivers, that's not something we've looked into, I don't think, so maybe that's the next route. Anyway, I JUST had another one: bp-f10452e1-dc50-482d-88a1-e56b80170424 And one from yesterday: bp-28bd1cf9-f7e4-4f26-9b10-405a00170424 Lastly, I'm not interested in having to start new profiles again and again unless it's going to tell us what's wrong with the existing one I'm using. We've already been the new profile route, anyway. And, like I'd tried pushing, perhaps it's my browser security settings as I was told it might be in the past, but you've not once talked about how that might be the problem. I want a single profile with my existing bookmarks. I've already made quite a few sacrifices to get this far such as deleting extensions and add-ons.
John99 971 solutions 13138 answers

No one is asking you to delete extensions, only to test without them when you have problems, or are intending to investigate problems, so that they may be ruled in or out of the problem. And of course if you test with a specific additional test profiles it should not interfere with your day to day browsing activities.

You can still have and keep a crashy hangy Firefox to use day to day on multiple sites with multiple add-ons, whilst having a well behaved non crashing none hanging test profile for comparison.

Something similar with new profiles. I am trying to work out what is changing in the profiles or is involved in the problems. It is still worth TESTING with new profiles. We can even then test with old profiles once we know the cause of an issue. If the issue is profile related it may be possible to recreate a hang or issue with that profile. It may even reproduce the problems for others when they test with that profile or particular files from that profile. If that is the case then engineers and others may look at the problem. Just do not expect anyone to be interested if it is with multiple add-ons, multiple sites and with memory running out, because it will not be worth trying to work on.

The same goes with Windows safe mode it is a troubleshooting step. It is not intended that you stay in Windows safe mode permanently, just that we try to work out whether or not that makes a significant difference or not.

What I am trying to do is basically a process of elimination. In son=me situations the Crash Signatures or results will indicate what is going wrong. We can be fairly certain your current crashes result from the use of Multi Process Firefox. However you appear to be reporting that multi mode Firefox is normally much faster for you and Firefox crawls in ordinary single process mode. Ideally multi mode Firefox is much faster but if single mode crawls that indicates you also have an issue with that.

Previous posts make me suspect you have multiple issues, however they are difficult to troubleshoot and help you with if you insist on using old profiles multiple sites, and multiple addons.

We were possibly making progress because it appears you get no crashes in certain configurations. Possibly in some configurations i.e. Windows safe mode you also get no hangs. Yet that may mean it is a Windows related issue, but if it relates to common Windows software or common hardware/drivers people may be able to troubleshoot and help you with it.

As for my last post I was just trying to quickly copy over information from the last thread but did not want to spend time on tidying up the formatting by hand.

We (or at least I ) still have no idea if we are staying on this forum software for days or months. (The software affects writing and localising of help articles not just providing support replies) If we revert back again quickly it causes minimal disruption. On the other hand the other forum software is decidedly flawed and it would make sense to try to fix the important flaws before using it again.

No one is asking you to delete extensions, only to test without them when you have problems, or are intending to investigate problems, so that they may be ruled in or out of the problem. And of course if you test with a specific additional test profiles it should not interfere with your day to day browsing activities. You can still have and keep a crashy hangy Firefox to use day to day on multiple sites with multiple add-ons, whilst having a well behaved non crashing none hanging test profile for comparison. Something similar with new profiles. I am trying to work out what is changing in the profiles or is involved in the problems. It is still worth TESTING with new profiles. We can even then test with old profiles once we know the cause of an issue. If the issue is profile related it may be possible to recreate a hang or issue with that profile. It may even reproduce the problems for others when they test with that profile or particular files from that profile. If that is the case then engineers and others may look at the problem. Just do not expect anyone to be interested if it is with multiple add-ons, multiple sites and with memory running out, because it will not be worth trying to work on. The same goes with Windows safe mode it is a troubleshooting step. It is not intended that you stay in Windows safe mode permanently, just that we try to work out whether or not that makes a significant difference or not. What I am trying to do is basically a process of elimination. In son=me situations the Crash Signatures or results will indicate what is going wrong. We can be fairly certain your current crashes result from the use of Multi Process Firefox. However you appear to be reporting that multi mode Firefox is normally much faster for you and Firefox crawls in ordinary single process mode. Ideally multi mode Firefox is much faster but if single mode crawls that indicates you also have an issue with that. Previous posts make me suspect you have multiple issues, however they are difficult to troubleshoot and help you with if you insist on using old profiles multiple sites, and multiple addons. '''We were possibly making progress because it appears you get no crashes in certain configurations. Possibly in some configurations i.e. Windows safe mode you also get no hangs.''' Yet that may mean it is a Windows related issue, but if it relates to common Windows software or common hardware/drivers people may be able to troubleshoot and help you with it. As for my last post I was just trying to quickly copy over information from the last thread but did not want to spend time on tidying up the formatting by hand. We (or at least I ) still have no idea if we are staying on this forum software for days or months. (The software affects writing and localising of help articles not just providing support replies) If we revert back again quickly it causes minimal disruption. On the other hand the other forum software is decidedly flawed and it would make sense to try to fix the important flaws before using it again.

Question owner

Would any of you suggest I join bugzilla? I looked at it and feel completely lost, so I'm not sure what help I'd be, but this still hasn't been resolved and I'm still getting the same crash reports.

bp-cd4ac36e-9350-4126-959e-081890170504 bp-50d3b255-30c6-4125-a053-8d7980170503 bp-a3500bf1-92fb-40f8-b21d-76c120170503 bp-6b04e71e-56be-4908-b7ec-11d2f0170502 bp-6d5b6a36-926a-406e-947f-089710170502

BTW, didn't even think of this, but here is my troubleshooting information:

Application Basics


Name: Firefox Version: 53.0 Build ID: 20170413192749 Update Channel: release User Agent: Mozilla/5.0 (Windows NT 6.1; rv:53.0) Gecko/20100101 Firefox/53.0 OS: Windows_NT 6.1 Multiprocess Windows: 1/1 (Enabled by default) Safe Mode: false

Crash Reports for the Last 3 Days


Report ID: bp-cd4ac36e-9350-4126-959e-081890170504 Submitted: 13 minutes ago

Report ID: bp-50d3b255-30c6-4125-a053-8d7980170503 Submitted: 1 day ago

Report ID: bp-a3500bf1-92fb-40f8-b21d-76c120170503 Submitted: 1 day ago

Report ID: bp-6b04e71e-56be-4908-b7ec-11d2f0170502 Submitted: 2 days ago

Report ID: bp-6d5b6a36-926a-406e-947f-089710170502 Submitted: 2 days ago

All Crash Reports

Extensions


Name: Application Update Service Helper Version: 2.0 Enabled: true ID: aushelper@mozilla.org

Name: Multi-process staged rollout Version: 1.14 Enabled: true ID: e10srollout@mozilla.org

Name: Pocket Version: 1.0.5 Enabled: true ID: firefox@getpocket.com

Name: Shield Recipe Client Version: 1.0.0 Enabled: true ID: shield-recipe-client@mozilla.org

Name: Web Compat Version: 1.0 Enabled: true ID: webcompat@mozilla.org

Graphics


Features Compositing: Direct3D 11 Asynchronous Pan/Zoom: wheel input enabled WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D11 vs_4_0 ps_4_0) WebGL2 Renderer: WebGL creation failed: * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Exhausted GL driver caps. Audio Backend: wasapi Direct2D: true DirectWrite: true (6.2.9200.22084) GPU #1 Active: Yes Description: Intel(R) HD Graphics Vendor ID: 0x8086 Device ID: 0x0046 Driver Version: 8.15.10.2993 Driver Date: 1-30-2013 Drivers: igdumdx32 igd10umd32 Subsys ID: 04101028 RAM: Unknown

Diagnostics AzureCanvasAccelerated: 0 AzureCanvasBackend: Direct2D 1.1 AzureCanvasBackend (UI Process): skia AzureContentBackend: Direct2D 1.1 AzureContentBackend (UI Process): skia AzureFallbackCanvasBackend (UI Process): cairo Decision Log D3D9_COMPOSITING: disabled by default: Disabled by default



Important Modified Preferences


accessibility.typeaheadfind.flashBar: 0 browser.cache.disk.capacity: 358400 browser.cache.disk.filesystem_reported: 1 browser.cache.disk.smart_size.first_run: false browser.cache.frecency_experiment: 1 browser.download.importedFromSqlite: true browser.places.smartBookmarksVersion: 8 browser.search.suggest.enabled: false browser.sessionstore.upgradeBackup.latestBuildID: 20170323105023 browser.startup.homepage: yahoo.com browser.startup.homepage_override.buildID: 20170413192749 browser.startup.homepage_override.mstone: 53.0 browser.tabs.remote.autostart.2: true browser.urlbar.autocomplete.enabled: false browser.urlbar.daysBeforeHidingSuggestionsPrompt: 2 browser.urlbar.lastSuggestionsPromptDate: 20170413 browser.urlbar.suggest.bookmark: false browser.urlbar.suggest.history: false browser.urlbar.suggest.openpage: false extensions.lastAppVersion: 53.0 gfx.crash-guard.d3d11layers.appVersion: 52.0.2 gfx.crash-guard.d3d11layers.deviceID: 0x0046 gfx.crash-guard.d3d11layers.driverVersion: 8.15.10.2993 gfx.crash-guard.d3d11layers.feature-d2d: true gfx.crash-guard.d3d11layers.feature-d3d11: true gfx.crash-guard.status.d3d11layers: 2 gfx.crash-guard.status.d3d9video: 2 media.gmp-gmpopenh264.abi: x86-msvc-x86 media.gmp-gmpopenh264.enabled: false media.gmp-gmpopenh264.lastUpdate: 1491895387 media.gmp-gmpopenh264.version: 1.6 media.gmp-manager.buildID: 20170413192749 media.gmp-manager.lastCheck: 1493889796 media.gmp-widevinecdm.abi: x86-msvc-x86 media.gmp-widevinecdm.enabled: false media.gmp-widevinecdm.lastUpdate: 1491895389 media.gmp-widevinecdm.version: 1.4.8.903 media.gmp.storage.version.observed: 1 media.hardware-video-decoding.failed: false network.cookie.prefsMigrated: true network.predictor.cleaned-up: true places.database.lastMaintenance: 1492062870 places.history.enabled: false places.history.expiration.transient_current_max_pages: 122334 plugin.disable_full_page_plugin_for_types: application/pdf privacy.history.custom: true privacy.sanitize.sanitizeOnShutdown: true privacy.trackingprotection.pbmode.enabled: false security.sandbox.content.tempDirSuffix: {81252e00-3c26-437a-b1c1-6771cf598733} services.sync.declinedEngines: storage.vacuum.last.index: 0 storage.vacuum.last.places.sqlite: 1492062870

Important Locked Preferences


Places Database


JavaScript


Incremental GC: true

Accessibility


Activated: false Prevent Accessibility: 0

Library Versions


NSPR Expected minimum version: 4.13.1 Version in use: 4.13.1

NSS Expected minimum version: 3.29.5 Version in use: 3.29.5

NSSSMIME Expected minimum version: 3.29.5 Version in use: 3.29.5

NSSSSL Expected minimum version: 3.29.5 Version in use: 3.29.5

NSSUTIL Expected minimum version: 3.29.5 Version in use: 3.29.5

Experimental Features


Sandbox


Content Process Sandbox Level: 1

Maybe that will help with something.

Would any of you suggest I join bugzilla? I looked at it and feel completely lost, so I'm not sure what help I'd be, but this still hasn't been resolved and I'm still getting the same crash reports. bp-cd4ac36e-9350-4126-959e-081890170504 bp-50d3b255-30c6-4125-a053-8d7980170503 bp-a3500bf1-92fb-40f8-b21d-76c120170503 bp-6b04e71e-56be-4908-b7ec-11d2f0170502 bp-6d5b6a36-926a-406e-947f-089710170502 BTW, didn't even think of this, but here is my troubleshooting information: Application Basics ------------------ Name: Firefox Version: 53.0 Build ID: 20170413192749 Update Channel: release User Agent: Mozilla/5.0 (Windows NT 6.1; rv:53.0) Gecko/20100101 Firefox/53.0 OS: Windows_NT 6.1 Multiprocess Windows: 1/1 (Enabled by default) Safe Mode: false Crash Reports for the Last 3 Days --------------------------------- Report ID: bp-cd4ac36e-9350-4126-959e-081890170504 Submitted: 13 minutes ago Report ID: bp-50d3b255-30c6-4125-a053-8d7980170503 Submitted: 1 day ago Report ID: bp-a3500bf1-92fb-40f8-b21d-76c120170503 Submitted: 1 day ago Report ID: bp-6b04e71e-56be-4908-b7ec-11d2f0170502 Submitted: 2 days ago Report ID: bp-6d5b6a36-926a-406e-947f-089710170502 Submitted: 2 days ago All Crash Reports Extensions ---------- Name: Application Update Service Helper Version: 2.0 Enabled: true ID: aushelper@mozilla.org Name: Multi-process staged rollout Version: 1.14 Enabled: true ID: e10srollout@mozilla.org Name: Pocket Version: 1.0.5 Enabled: true ID: firefox@getpocket.com Name: Shield Recipe Client Version: 1.0.0 Enabled: true ID: shield-recipe-client@mozilla.org Name: Web Compat Version: 1.0 Enabled: true ID: webcompat@mozilla.org Graphics -------- Features Compositing: Direct3D 11 Asynchronous Pan/Zoom: wheel input enabled WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D11 vs_4_0 ps_4_0) WebGL2 Renderer: WebGL creation failed: * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Exhausted GL driver caps. Audio Backend: wasapi Direct2D: true DirectWrite: true (6.2.9200.22084) GPU #1 Active: Yes Description: Intel(R) HD Graphics Vendor ID: 0x8086 Device ID: 0x0046 Driver Version: 8.15.10.2993 Driver Date: 1-30-2013 Drivers: igdumdx32 igd10umd32 Subsys ID: 04101028 RAM: Unknown Diagnostics AzureCanvasAccelerated: 0 AzureCanvasBackend: Direct2D 1.1 AzureCanvasBackend (UI Process): skia AzureContentBackend: Direct2D 1.1 AzureContentBackend (UI Process): skia AzureFallbackCanvasBackend (UI Process): cairo Decision Log D3D9_COMPOSITING: disabled by default: Disabled by default Important Modified Preferences ------------------------------ accessibility.typeaheadfind.flashBar: 0 browser.cache.disk.capacity: 358400 browser.cache.disk.filesystem_reported: 1 browser.cache.disk.smart_size.first_run: false browser.cache.frecency_experiment: 1 browser.download.importedFromSqlite: true browser.places.smartBookmarksVersion: 8 browser.search.suggest.enabled: false browser.sessionstore.upgradeBackup.latestBuildID: 20170323105023 browser.startup.homepage: yahoo.com browser.startup.homepage_override.buildID: 20170413192749 browser.startup.homepage_override.mstone: 53.0 browser.tabs.remote.autostart.2: true browser.urlbar.autocomplete.enabled: false browser.urlbar.daysBeforeHidingSuggestionsPrompt: 2 browser.urlbar.lastSuggestionsPromptDate: 20170413 browser.urlbar.suggest.bookmark: false browser.urlbar.suggest.history: false browser.urlbar.suggest.openpage: false extensions.lastAppVersion: 53.0 gfx.crash-guard.d3d11layers.appVersion: 52.0.2 gfx.crash-guard.d3d11layers.deviceID: 0x0046 gfx.crash-guard.d3d11layers.driverVersion: 8.15.10.2993 gfx.crash-guard.d3d11layers.feature-d2d: true gfx.crash-guard.d3d11layers.feature-d3d11: true gfx.crash-guard.status.d3d11layers: 2 gfx.crash-guard.status.d3d9video: 2 media.gmp-gmpopenh264.abi: x86-msvc-x86 media.gmp-gmpopenh264.enabled: false media.gmp-gmpopenh264.lastUpdate: 1491895387 media.gmp-gmpopenh264.version: 1.6 media.gmp-manager.buildID: 20170413192749 media.gmp-manager.lastCheck: 1493889796 media.gmp-widevinecdm.abi: x86-msvc-x86 media.gmp-widevinecdm.enabled: false media.gmp-widevinecdm.lastUpdate: 1491895389 media.gmp-widevinecdm.version: 1.4.8.903 media.gmp.storage.version.observed: 1 media.hardware-video-decoding.failed: false network.cookie.prefsMigrated: true network.predictor.cleaned-up: true places.database.lastMaintenance: 1492062870 places.history.enabled: false places.history.expiration.transient_current_max_pages: 122334 plugin.disable_full_page_plugin_for_types: application/pdf privacy.history.custom: true privacy.sanitize.sanitizeOnShutdown: true privacy.trackingprotection.pbmode.enabled: false security.sandbox.content.tempDirSuffix: {81252e00-3c26-437a-b1c1-6771cf598733} services.sync.declinedEngines: storage.vacuum.last.index: 0 storage.vacuum.last.places.sqlite: 1492062870 Important Locked Preferences ---------------------------- Places Database --------------- JavaScript ---------- Incremental GC: true Accessibility ------------- Activated: false Prevent Accessibility: 0 Library Versions ---------------- NSPR Expected minimum version: 4.13.1 Version in use: 4.13.1 NSS Expected minimum version: 3.29.5 Version in use: 3.29.5 NSSSMIME Expected minimum version: 3.29.5 Version in use: 3.29.5 NSSSSL Expected minimum version: 3.29.5 Version in use: 3.29.5 NSSUTIL Expected minimum version: 3.29.5 Version in use: 3.29.5 Experimental Features --------------------- Sandbox ------- Content Process Sandbox Level: 1 Maybe that will help with something.

Modified by FireFoxFan1

John99 971 solutions 13138 answers

Bugzilla only really helps if we get in to a position to file a good bug about your specific issues that has a chance of being looked at. Bugzilla is not a discussion forum. It is a work place for the engineers and developers working on the issues.

Only the most important bugs ever get attention. We have something like 300 bugs open relating to problems with our support forum software at present, and we still are not sure how long before we will move back to the other forum software or how long before problems will be fixed. Your old profile and posts are now accessible in read only form here:

Looking at the first crash ID above bp-cd4ac36e-9350-4126-959e-081890170504 Firefox 53.0 Crash Report [@ IPCError-browser | ShutDownKill ] That will not happen if you disable multi process Firefox. It is a problem & resultant Crash Signature that could well have many different causes. As you can see the crash signature lists over a dozen bugs as being related.

Bugzilla only really helps if we get in to a position to file a good bug about your specific issues that has a chance of being looked at. Bugzilla is not a discussion forum. It is a work place for the engineers and developers working on the issues. Only the most important bugs ever get attention. We have something like 300 bugs open relating to problems with our support forum software at present, and we still are not sure how long before we will move back to the other forum software or how long before problems will be fixed. Your old profile and posts are now accessible in read only form here: * https://hwsfp35778.lithium.com/t5/user/viewprofilepage/user-id/834815 * https://hwsfp35778.lithium.com/t5/Firefox/This-Week-s-Series-of-Firefox-Crashes/m-p/1391008#M1047426 Looking at the first crash ID above bp-cd4ac36e-9350-4126-959e-081890170504 Firefox 53.0 Crash Report [@ IPCError-browser | ShutDownKill ] That will not happen if you disable multi process Firefox. It is a problem & resultant Crash Signature that could well have many different causes. As you can see the crash signature lists over a dozen bugs as being related.

Question owner

Okay, something else that can be ruled out. I tried a totally new profile (multi-process turned on, of course, and hardware acceleration turned off), and got the same crash:

bp-02e15f6c-01c5-443a-9548-80ee40170505

So this isn't the result of a corrupt profile. Perhaps someone can look into my troubleshooting information above and see if they see anything unusual. Something that caught me eye (but may mean nothing) was this:

WebGL2 Renderer: WebGL creation failed: * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Exhausted GL driver caps.

Also, my goal in all of this?

To be able to run Firefox with multiprocess enabled without crashes related to it, since disabling it makes the browser run slowly and then freeze.

Okay, something else that can be ruled out. I tried a totally new profile (multi-process turned on, of course, and hardware acceleration turned off), and got the same crash: bp-02e15f6c-01c5-443a-9548-80ee40170505 So this isn't the result of a corrupt profile. Perhaps someone can look into my troubleshooting information above and see if they see anything unusual. Something that caught me eye (but may mean nothing) was this: WebGL2 Renderer: WebGL creation failed: * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Error during ANGLE OpenGL init. * Exhausted GL driver caps. Also, my goal in all of this? To be able to run Firefox with multiprocess enabled without crashes related to it, since disabling it makes the browser run slowly and then freeze.

Modified by FireFoxFan1

John99 971 solutions 13138 answers

That is a good goal and should be achievable.

To be able to run Firefox with multiprocess enabled 
without crashes related to it, 
since disabling it makes the browser run slowly and then freeze.

However for troubleshooting and a realistic prospect of progress you need to initially revise that to a first goal of

To be able to run Firefox without crashes and  freezes.

I am fairly sure we have already discovered methods of you running Firefox without crashes.

Multi process is intended to speed up Firefox, but does in some circumstances cause problems.

If you have issues in single process Firefox you must sort them out first before compounding your problems by using a multi process Firefox.

Once multi process Firefox is more stable and tested, in a few versions time, I may be saying the opposite and if some one has a slow Firefox saying they should use multi process Firefox because it is faster. Right now that is not always the case.

You are; if I recall correctly; not talking about minor issues in single process Firefox, I think you mentioned it crawling and freezing. That should not be happening.

What did you do in that 3 hour session that resulted in bp-02e15f6c-01c5-443a-9548-80ee40170505 could you try repeating that or something very similar in a single process Firefox.

Just how bad is Firefox in single process mode windows safe mode and using a single website ?

In that mode in a new profile are you able to get Firefox to freeze ?

  • If so how do you do that ?
  • If you are able to reproduce that please preserve the profile used by backing it up and not reusing that profile.
  • You and others can later test that profile to see if it recreates the issue, if so we are on the way to being able to reproduce the issue and ask a developer to look in to the problem.
  • And we should be able to take further steps to investigate your freezes using a profiler or built in tool.
That is a good goal and should be achievable. To be able to run Firefox with multiprocess enabled without crashes related to it, since disabling it makes the browser run slowly and then freeze. However for troubleshooting and a realistic prospect of progress you need to initially revise that to a first goal of To be able to run Firefox without crashes and freezes. I am fairly sure we have already discovered methods of you running Firefox without crashes. Multi process is intended to speed up Firefox, but does in some circumstances cause problems. If you have issues in single process Firefox you must sort them out first before compounding your problems by using a multi process Firefox. Once multi process Firefox is more stable and tested, in a few versions time, I may be saying the opposite and if some one has a slow Firefox saying they should use multi process Firefox because it is faster. Right now that is not always the case. You are; if I recall correctly; not talking about minor issues in single process Firefox, I think you mentioned it crawling and freezing. That should not be happening. What did you do in that 3 hour session that resulted in bp-02e15f6c-01c5-443a-9548-80ee40170505 could you try repeating that or something very similar in a single process Firefox. Just how bad is Firefox in single process mode windows safe mode and using a single website ? In that mode in a new profile are you able to get Firefox to freeze ? * If so how do you do that ? * If you are able to reproduce that please preserve the profile used by backing it up and not reusing that profile. * You and others can later test that profile to see if it recreates the issue, if so we are on the way to being able to reproduce the issue and ask a developer to look in to the problem. * And we should be able to take further steps to investigate your freezes using a profiler or built in tool.

Question owner

John99 said What did you do in that 3 hour session that resulted in bp-02e15f6c-01c5-443a-9548-80ee40170505 could you try repeating that or something very similar in a single process Firefox. Just how bad is Firefox in single process mode windows safe mode and using a single website ? In that mode in a new profile are you able to get Firefox to freeze ?
  • If so how do you do that ?
  • If you are able to reproduce that please preserve the profile used by backing it up and not reusing that profile.
  • You and others can later test that profile to see if it recreates the issue, if so we are on the way to being able to reproduce the issue and ask a developer to look in to the problem.
  • And we should be able to take further steps to investigate your freezes using a profiler or built in tool.

As I've explained before - and this has been what's made it difficult - is that the crashes are not site specific. There is not one thing I do or don't do while browsing that replicates the crashes. The only constant is that the crashes happen later rather than sooner in a session. It seems to be an issue of time and building up a session (maybe memory related)?

What I will do is use a new profile and turn off multi-process. As to your last two points, I wouldn't even know how to go about that process. I am even more skeptical about this this time, however, since you're still asking me to pinpoint - even generally - what causes these crashes. Since they aren't site specific, I'd not be asking you guys if I had any idea. There is no one site or even a group of sites. Aside from time being a factor in the crashes, the only other thing I can think of is that it seems very slightly more common when I go to a graphic-intensive webpage (maybe something with lots of dynamic ads, auto-play videos, lots and lots of gifs). Obviously, this in that case it's probably a memory issue. But this happens even when just browsing simple newspapers in multiple tabs.

Lastly, what do you mean by "backing up" this profile when I get the crash?

<blockquote>''John99 [[#answer-965291|said]]'' What did you do in that 3 hour session that resulted in bp-02e15f6c-01c5-443a-9548-80ee40170505 could you try repeating that or something very similar in a single process Firefox. Just how bad is Firefox in single process mode windows safe mode and using a single website ? In that mode in a new profile are you able to get Firefox to freeze ? * If so how do you do that ? * If you are able to reproduce that please preserve the profile used by backing it up and not reusing that profile. * You and others can later test that profile to see if it recreates the issue, if so we are on the way to being able to reproduce the issue and ask a developer to look in to the problem. * And we should be able to take further steps to investigate your freezes using a profiler or built in tool. </blockquote> As I've explained before - and this has been what's made it difficult - is that the crashes are not site specific. There is not one thing I do or don't do while browsing that replicates the crashes. The only constant is that the crashes happen later rather than sooner in a session. It seems to be an issue of time and building up a session (maybe memory related)? What I will do is use a new profile and turn off multi-process. As to your last two points, I wouldn't even know how to go about that process. I am even more skeptical about this this time, however, since you're still asking me to pinpoint - even generally - what causes these crashes. Since they aren't site specific, I'd not be asking you guys if I had any idea. There is no one site or even a group of sites. Aside from time being a factor in the crashes, the only other thing I can think of is that it seems very slightly more common when I go to a graphic-intensive webpage (maybe something with lots of dynamic ads, auto-play videos, lots and lots of gifs). Obviously, this in that case it's probably a memory issue. But this happens even when just browsing simple newspapers in multiple tabs. Lastly, what do you mean by "backing up" this profile when I get the crash?

Modified by FireFoxFan1