X
Tocca qui per la versione per piattaforma mobile del sito.

Forum di supporto

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Daily Crash Reports Continued...

Inserita

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

Modificato da FireFoxFan1 il

Dettagli aggiuntivi sul sistema

Plugin installati

Three, but all permanently disabled.

Applicazione

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

Estensioni

  • 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) (Inattiva)

Javascript

  • incrementalGCEnabled: True

Grafica

  • 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

Preferenze modificate

Varie

  • User JS: No
  • Accessibilità: No

Utente che ha posto la domanda

Got this while navigating through theroot.com, which has some pretty bad autoplay ads at the moment that pull you up and down the page no matter where you are on the page:

bp-7930924c-1463-4ba8-9793-e20d81170912

Got this while navigating through theroot.com, which has some pretty bad autoplay ads at the moment that pull you up and down the page no matter where you are on the page: bp-7930924c-1463-4ba8-9793-e20d81170912

Utente che ha posto la domanda

cor-el said

Yes, this last report looks as caused by the Malwarebytes Exploit Protection feature. Try this:
  • Malwarebytes: turn off Real-Time Protection -> Exploit Protection

Okay, so turning off Real-Time Protection in Malwarebytes did in fact result in fewer hangs (crashes), but after trying to open up three PDF files right now, I'm back to...

bp-2fa28e3d-8ec0-45e0-8df2-3ce740170913

ntdll.dll@0x63679 ntdll.dll@0x6364c

''cor-el [[#answer-1005805|said]]'' <blockquote> Yes, this last report looks as caused by the Malwarebytes Exploit Protection feature. Try this: *Malwarebytes: turn off Real-Time Protection -> Exploit Protection </blockquote> Okay, so turning off Real-Time Protection in Malwarebytes did in fact result in fewer hangs (crashes), but after trying to open up three PDF files right now, I'm back to... bp-2fa28e3d-8ec0-45e0-8df2-3ce740170913 ntdll.dll@0x63679 ntdll.dll@0x6364c
cor-el
  • Top 10 Contributor
  • Moderator
17470 soluzioni 157890 risposte

The crash report in a shutdown hang that still looks related to multi-process. IPC = Inter Process Communication and is used to communicate between various Firefox processes used with multi-process (this includes plugin-container). I'm still curious what crash reports you get with multi-process disabled.

The crash report in a shutdown hang that still looks related to multi-process. IPC = Inter Process Communication and is used to communicate between various Firefox processes used with multi-process (this includes plugin-container). I'm still curious what crash reports you get with multi-process disabled.

Utente che ha posto la domanda

cor-el said

I'm still curious what crash reports you get with multi-process disabled.

I'm pretty sure back on the first few pages we covered this, but I'll try again if you'd like.

''cor-el [[#answer-1006412|said]]'' <blockquote> I'm still curious what crash reports you get with multi-process disabled. </blockquote> I'm pretty sure back on the first few pages we covered this, but I'll try again if you'd like.

Utente che ha posto la domanda

cor-el said

I'm still curious what crash reports you get with multi-process disabled.

Okay, so I turned off multi-process. Same report:

bp-acefb7db-a303-4c1c-9825-d97a30170914

''cor-el [[#answer-1006412|said]]'' <blockquote>I'm still curious what crash reports you get with multi-process disabled.</blockquote> Okay, so I turned off multi-process. Same report: bp-acefb7db-a303-4c1c-9825-d97a30170914
cor-el
  • Top 10 Contributor
  • Moderator
17470 soluzioni 157890 risposte

This crash report still shows "DOMIPCEnabled : 1" indicating that multi-process is enabled ??

I see: Process Type = content (web), so this is related to one of the web processes that run in a separate processor thread and is possibly memory cleanup related (I see mentions of cycle collector (nsCycleCollector) in the crashing thread).

This crash report still shows "<b>DOMIPCEnabled : 1</b>" indicating that multi-process is enabled ?? I see: <b>Process Type = content (web)</b>, so this is related to one of the web processes that run in a separate processor thread and is possibly memory cleanup related (I see mentions of cycle collector (nsCycleCollector) in the crashing thread).

Utente che ha posto la domanda

cor-el said

This crash report still shows "DOMIPCEnabled : 1" indicating that multi-process is enabled ?? I see: Process Type = content (web), so this is related to one of the web processes that run in a separate processor thread and is possibly memory cleanup related (I see mentions of cycle collector (nsCycleCollector) in the crashing thread).

I'm confused. Before submitting that last report, I did what I've been told to do to disable multiprocess, setting browser.tabs.remote.autostart and browser.tabs.remote.autostart.2 to "false." Only one process was running in my Windows task manager. I've turned the second back to "true" (first is always set to "false") since because working with multiprocess disabled means complete freezes I have to use the task manager to close out of firefox. At least in the other case I can usually close with the "x" or through the "file" dropdown.

Anyway, got the same crash post title just now, though this one seems different in that this is the only file affected on the "Crashing Thread" (xul.dll):

bp-abf29153-cbe7-4f75-9250-7e4380170918

Literally four more today after the one above. It seems to involve "xul.dll" which I see in a simple google search is something Firefox has a lot of problems with. Not sure why it's acting up now.

bp-c2260836-7086-494b-8050-2cff61170918 bp-3197f10e-b27c-4abc-967a-cc61e0170918 bp-ce66aac6-17e7-49b3-8321-519f20170919 bp-7e14f59e-2670-4bf5-866e-e558d0170919

What's the easiest fix for a possibily corrupted xul.dll file?

More minutes apart. Had to close out manually because of the freezes:

bp-8833b56e-edd5-411b-ae70-a10cc0170919 bp-2d9f3d70-ca68-460a-bdb0-e844b1170919

''cor-el [[#answer-1006801|said]]'' <blockquote> This crash report still shows "<b>DOMIPCEnabled : 1</b>" indicating that multi-process is enabled ?? I see: <b>Process Type = content (web)</b>, so this is related to one of the web processes that run in a separate processor thread and is possibly memory cleanup related (I see mentions of cycle collector (nsCycleCollector) in the crashing thread). </blockquote> I'm confused. Before submitting that last report, I did what I've been told to do to disable multiprocess, setting browser.tabs.remote.autostart and browser.tabs.remote.autostart.2 to "false." Only one process was running in my Windows task manager. I've turned the second back to "true" (first is always set to "false") since because working with multiprocess disabled means complete freezes I have to use the task manager to close out of firefox. At least in the other case I can usually close with the "x" or through the "file" dropdown. Anyway, got the same crash post title just now, though this one seems different in that this is the only file affected on the "Crashing Thread" (xul.dll): bp-abf29153-cbe7-4f75-9250-7e4380170918 Literally four more today after the one above. It seems to involve "xul.dll" which I see in a simple google search is something Firefox has a lot of problems with. Not sure why it's acting up now. bp-c2260836-7086-494b-8050-2cff61170918 bp-3197f10e-b27c-4abc-967a-cc61e0170918 bp-ce66aac6-17e7-49b3-8321-519f20170919 bp-7e14f59e-2670-4bf5-866e-e558d0170919 What's the easiest fix for a possibily corrupted xul.dll file? More minutes apart. Had to close out manually because of the freezes: bp-8833b56e-edd5-411b-ae70-a10cc0170919 bp-2d9f3d70-ca68-460a-bdb0-e844b1170919

Modificato da FireFoxFan1 il

Utente che ha posto la domanda

What's the xul.dll file? It seems to be popping up in all my recent crash reports. Just now:

bp-602f5a05-352a-471d-a70c-d8d410170922

Usually happens on pages with autoplay videos, and maybe when I close out of them before they are finished.

As I said, I recently refreshed this, so maybe it's not the result of a faulty .dll file? What else would it be?

What's the xul.dll file? It seems to be popping up in all my recent crash reports. Just now: bp-602f5a05-352a-471d-a70c-d8d410170922 Usually happens on pages with autoplay videos, and maybe when I close out of them before they are finished. As I said, I recently refreshed this, so maybe it's not the result of a faulty .dll file? What else would it be?
cor-el
  • Top 10 Contributor
  • Moderator
17470 soluzioni 157890 risposte

XUL.dll is the main Firefox file that contains all basic code (look at its file size in the Firefox program folder; firefox.exe is a small file with the startup code), so it isn't a surprise that you will see this file showing up in a lot of crash reports.

XUL.dll is the main Firefox file that contains all basic code (look at its file size in the Firefox program folder; firefox.exe is a small file with the startup code), so it isn't a surprise that you will see this file showing up in a lot of crash reports.