This bug was filed from the Socorro interface and is report bp-b50d4d00-6ba8-4b56-8787-f6be00170624. ============================================================= This is topcrash #5 in the Windows nightlies of 20170622030208. Looks like it is profiler or, really, hang-detector, related.
Hello NVidia drivers, my old friends...
No progress on this bug yet? I have been crashing since firefox 54 I believe, and am still crashing on Firefox 56 beta. Just a CTD with no crash report or error message generated. Event viewer shows event ID 1000 application error : Faulting application name: firefox.exe, version: 188.8.131.5236, time stamp: 0x59931079 Faulting module name: nvd3d9wrapx.dll, version: 184.108.40.20628, time stamp: 0x598b835f Exception code: 0xc0000005 Fault offset: 0x00000000000028bb Faulting process id: 0xbb0 Faulting application start time: 0x01d317be057ea3a9 Faulting application path: C:\Program Files\Mozilla Firefox\firefox.exe Faulting module path: C:\Program Files\NVIDIA Corporation\CoProcManager\nvd3d9wrapx.dll Report Id: 57413e6d-83b9-11e7-8296-7c11be384500 Firefox managed to generate a few crash reports when it started happening again but it has since stopped generating crash reports, so im not sure if its the same issue. https://crash-stats.mozilla.com/report/index/bp-d3714b5f-2c9e-4c63-a98d-bd5740170817 According to jya in the firefox IRC channel, firefox hangs and then it crashes when the profiler is trying to retrieve my system information or something like that, but there is no way to stop it from retrieving my system information to prevent the crash. Disabling auto send technical data in options didnt stop the crash, and turning it back on doesnt cause it to generate any more crash reports.
#3 top crash on the 9-20 Nightly, with 356 crashes from 6 installations.
Is there still no progress on this? What's going on? I've been stuck on ESR for months because the newer firefox versions just keep crashing without generating any crash reports.
Is it possible to add a blacklist so we can skip collecting info from nvd3d9wrapx.dll?
Crash Signature: [@ nvd3d9wrapx.dll@0x28bb] → [@ nvd3d9wrapx.dll@0x28bb] [@ nvd3d9wrap.dll@0xcf0d ]
(In reply to Kan-Ru Chen [:kanru] (UTC+8) from comment #5) > Is it possible to add a blacklist so we can skip collecting info from > nvd3d9wrapx.dll? When this crash is happening we aren't collecting hang information from a specific DLL, rather we're trying to process the hang information we had previously collected. In order for us to get native stack information for a stack frame we need the offset in memory of the DLLs which are currently loaded, so we can transform addresses into module offset information, and this crash is occurring in profiler code which is requesting this information. Theoretically if you have extended telemetry disabled, this could should never run, even in nightly. In addition, this code should be disabled via a compile time flag outside of nightly. If this problem also reproduces in devedition 57, then I definitely want to see a stack from it. (In reply to Anonymous from comment #4) > Is there still no progress on this? What's going on? I've been stuck on ESR > for months because the newer firefox versions just keep crashing without > generating any crash reports. This code shouldn't run anywhere outside of nightly - it's disabled at compile time in beta and release builds. Are you also running into crashes there?
Flags: needinfo?(michael) → needinfo?(question2005)
You need to log in before you can comment on or make changes to this bug.