User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36

Steps to reproduce:

Random crashes (5-60m usage), not related to specific webpage, module, profile or windows version.
Crashes started after Windows 10 upgrade (3 different computers total, different Windows versions).

Firefox crashed, similarly to older similar crashes related to different AV problems, causing ntdll.dll crash:
https://bugzilla.mozilla.org/show_bug.cgi?id=1509748
https://bugzilla.mozilla.org/show_bug.cgi?id=1564079

Tried:

• Temp data delete (incl programfiles folders)
• FF reinstall
• Profile reset
• EAF override from Windows Security panel

One computer has AV installed, other two does not have additional AV software installed currently.

Windows versions:
PC no 2 - Windows 10 20H2 - 19042.867 <- Crashes started after upg to W10 20H2 version, prev version was. F-secure AV installed on this one. EAF bypass worked on 1909, on 20H2 also overridden but no effect on crash
PC no 2 - Windows 10 2004 - 19041.867 <- Crashes started on W10 version 1909. No additional AV installed, tried clean profile, reinstall of FF, EAF bypass
PC no 2 - Windows 10 1909 <- Also crashes with same error, version of FF needs to be specified. EAF bypass enabled, no effect.

Actual results:

Faulting application name: firefox.exe, version: 87.0.0.7747, time stamp: 0x60533c0c
Faulting module name: ntdll.dll, version: 10.0.19041.844, time stamp: 0x60a6ca36
Exception code: 0xc0000005
Fault offset: 0x000000000002d7bd
Faulting process id: 0x4810
Faulting application start time: 0x01d72606fa6ca964
Faulting application path: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 4cda442e-d3c6-4644-8db2-107e34dfd3ff
Faulting package full name:
Faulting package-relative application ID:

Expected results:

The process should not have crashed at least on one computer, now all of my three computers have crashing and unusable FF.

Additional information from event viewer:
Fault bucket 1818949430642731467, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: firefox.exe
P2: 87.0.0.7747
P3: 60533c0c
P4: ntdll.dll
P5: 10.0.19041.844
P6: 60a6ca36
P7: 000000000008c57f
P8: c0000409
P9: 000000000000000a
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF353.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF671.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6A1.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6AF.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6EE.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_firefox.exe_1fff1a47c28e89b6452fcd582bf3bd0a426d4ed_9b234b83_12ab52e1-8638-4c19-94e2-b376ffcadb0c

Analysis symbol:
Rechecking for solution: 0
Report Id: 7ccd50e5-cb8e-40c4-a288-9ba11d19dc53
Report Status: 268435456
Hashed bucket: 75636ba852a152b9193e34deb5dbe9cb
Cab Guid: 0

Windows Error Report of crash event

Second Windows error report file

The Bugbug bot thinks this bug should belong to the 'Firefox Build System::General' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Hey Madis can you try to use Firefox for a couple of days on the nightly build as well. Download the build from : https://www.mozilla.org/en-US/firefox/nightly/all/ .
Can you test the issue while in Safe Mode? You can find helpful info here : https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode .

Andrew can you help us with this issue? Can you make anything out of the attached reports?

Hey Andrei!

Sure, will do and provide feedback to you in couple of days, say in the end of week.

Additionally, in safe mode the version of firefox regular build or nightly? I assume you meant regular build actually and provide extra information.

Hey Andrei!

Well, nighlty build crashed almost right away on one computer, will try safe mode and see if I can get any additional information from multiple devices. I will get back with logs in few hours.

Fault bucket 1857691717276258356, type 5
Event Name: FaultTolerantHeap
Response: Not available
Cab Id: 0

Problem signature:
P1: firefox.exe
P2: 89.0.0.7773
P3: 607620E9
P4: ffffbaad
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
\?\C:\WINDOWS\SERVIC1\LOCALS1\AppData\Local\Temp\FTH31D5.tmp\fthempty.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31F5.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3215.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3210.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3250.tmp.txt

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: cb04bb2c-7588-48d9-92b8-9fb9f5ef2b57
Report Status: 268435456
Hashed bucket: e030aab76978317c39c7d8c63e6fd034
Cab Guid: 0

(In reply to Madis from comment #7)

Hey Andrei!

Well, nighlty build crashed almost right away on one computer, will try safe mode and see if I can get any additional information from multiple devices. I will get back with logs in few hours.

Nightly build report contents:
BuildID: 20210413214314
CrashTime: 1618400717
InstallTime: 1618400511
ModuleSignatureInfo: {"Microsoft Corporation":["msvcp140.dll","VCRUNTIME140.dll","VCRUNTIME140_1.dll"],"Microsoft Windows":["MpOAV.dll","wscapi.dll","ntshrui.dll","cscapi.dll","srvcli.dll","dbgcore.dll","dbghelp.dll","webauthn.dll","wininet.dll","AudioSes.dll","usp10.dll","cdp.dll","NapiNSP.dll","pnrpnsp.dll","wshbth.dll","winrnr.dll","ondemandconnroutehelper.dll","directmanipulation.dll","rasadhlp.dll","FWPUCLNT.DLL","OneCoreCommonProxyStub.dll","twinapi.dll","TaskFlowDataEngine.dll","Windows.Globalization.dll","DWrite.dll","comctl32.dll","MMDevAPI.dll","BCP47mrm.dll","InputHost.dll","textinputframework.dll","Windows.UI.dll","Bcp47Langs.dll","iertutil.dll","urlmon.dll","explorerframe.dll","amsi.dll","winhttp.dll","wbemsvc.dll","fastprox.dll","winmm.dll","wbemcomn.dll","dhcpcsvc6.DLL","dhcpcsvc.dll","wbemprox.dll","npmproxy.dll","WinSCard.dll","cryptnet.dll","version.dll","winnsi.dll","OneCoreUAPCommonProxyStub.dll","policymanager.dll","dataexchange.dll","ColorAdapterClient.dll","mscms.dll","twinapi.appcore.dll","avrt.dll","netprofm.dll","taskschd.dll","nlaapi.dll","propsys.dll","linkinfo.dll","wsock32.dll","wtsapi32.dll","dsreg.dll","WinTypes.dll","d3d11.dll","dcomp.dll","CoreUIComponents.dll","CoreMessaging.dll","apphelp.dll","uxtheme.dll","dwmapi.dll","kernel.appcore.dll","windows.storage.dll","gpapi.dll","dxgi.dll","ntmarta.dll","rsaenh.dll","msvcp110_win.dll","IPHLPAPI.DLL","dnsapi.dll","mswsock.dll","cryptsp.dll","CRYPTBASE.DLL","wldp.dll","ntasn1.dll","winsta.dll","ncrypt.dll","msasn1.dll","devobj.dll","umpdc.dll","powrprof.dll","sspicli.dll","userenv.dll","profapi.dll","ucrtbase.dll","bcrypt.dll","msvcp_win.dll","bcryptPrimitives.dll","win32u.dll","gdi32full.dll","crypt32.dll","cfgmgr32.dll","KERNELBASE.dll","wintrust.dll","imagehlp.dll","clbcatq.dll","ws2_32.dll","psapi.dll","msvcrt.dll","sechost.dll","user32.dll","setupapi.dll","rpcrt4.dll","shell32.dll","advapi32.dll","kernel32.dll","msctf.dll","ole32.dll","oleaut32.dll","shlwapi.dll","SHCore.dll","combase.dll","gdi32.dll","nsi.dll","imm32.dll","ntdll.dll","KBDUK.DLL","resourcepolicyclient.dll"],"Mozilla Corporation":["firefox.exe","xul.dll","nss3.dll","freebl3.dll","mozglue.dll","nssckbi.dll","osclientcerts.dll","softokn3.dll","lgpllibs.dll"],"RIIGI INFOSUSTEEMI AMET":["onepin-opensc-pkcs11.dll"]}
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: nightly
Throttleable: 1
URL:
Vendor: Mozilla
Version: 89.0a1

This report also contains technical information about the state of the application when it crashed.

Event log information:
Fault bucket 1857691717276258356, type 5
Event Name: FaultTolerantHeap
Response: Not available
Cab Id: 0

Problem signature:
P1: firefox.exe
P2: 89.0.0.7773
P3: 607620E9
P4: ffffbaad
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
\?\C:\WINDOWS\SERVIC1\LOCALS1\AppData\Local\Temp\FTH31D5.tmp\fthempty.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER31F5.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3215.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3210.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3250.tmp.txt

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: cb04bb2c-7588-48d9-92b8-9fb9f5ef2b57
Report Status: 268435456
Hashed bucket: e030aab76978317c39c7d8c63e6fd034
Cab Guid: 0

Gsvelto is probably a better person to ask.

I'm experiencing several crashes a day since updating to 87.0. Each and every crash appears to be instigated by mouse activity inside FF's window. No other application shows this behaviour.

Running:

• Win7 64bit
• FF 87.0
• HTTPS Everywhere
• ImTranslator
• uBlock Origin
• Enhancer for YouTube

This is how it was and never gave me problems. The only changes since the previous FF release that I can recall are going to 87.0 and updated Enhancer for YouTube to 2.0.104.5.

Tried and failed (still crashing):

• FF ESR
• Turned off Enhancer for YouTube
• Used a different HTTPS solution
• Turned off ImTranslator.
• Turned off Hardware Acceleration

I cannot reproduce this at will.

It seems clear that the bug is inside FF. The bug does NOT crash the processor, it locks the screen. The mouse pointer sometimes freezes right away too but sometimes it keeps responding for a couple of seconds. Ctrl+Alt+Del or any other command does not work so we can safely assume the keyboard is locked out also.

The crashes you posted are different from each other and they have different reasons which is odd because they're most certainly caused by different problems. Are there any recorded crashes in the about:crashes page? If not could you send me the .dmp files under C:\ProgramData\Microsoft\Windows\WER\Temp\ for analysis? Don't attach them to this bug, send them to me via e-mail.

You could also try with Firefox Nightly and see if it behaves differently.

Dear Gabriele,

As I mentioned, I've got three different devices. I will include logs from both of these computers and from this on, logs will be categorised as following:

• Computer 1 - Laptop
• Computer 2 - Desktop
• Computer 3 - Desktop 2

Initial logs were from laptop and second was from desktop. Desktop computer 2 additional error reports are now submitted using internal method, will I still send WERs for analysis on your email? Please read my previous answer, nightly behaves same manner, crashed almost immidiately.
Report ID Date Submitted
bp-00bec76a-f506-49f1-b309-27d0e0210416 4/16/2021, 11:48 AM
View
bp-c93c5d25-28be-4fb6-a580-de1910210416 4/16/2021, 11:48 AM
View
bp-0f1817ea-034e-4444-9e9f-e70e60210414 4/14/2021, 2:52 PM

(In reply to Madis from comment #12)

Initial logs were from laptop and second was from desktop. Desktop computer 2 additional error reports are now submitted using internal method, will I still send WERs for analysis on your email?

Yes that would be helpful.

Please read my previous answer, nightly behaves same manner, crashed almost immidiately.
Report ID Date Submitted
bp-00bec76a-f506-49f1-b309-27d0e0210416 4/16/2021, 11:48 AM
View
bp-c93c5d25-28be-4fb6-a580-de1910210416 4/16/2021, 11:48 AM
View

These two crashes are from version 74 so they're unlikely to be recent.

bp-0f1817ea-034e-4444-9e9f-e70e60210414 4/14/2021, 2:52 PM

This crash is more interesting. I see that you have an old version of OpenSC installed (0.20.1.920), this might be causing the odd crashes. We had them reported before in bug 1560486 among others. You might want to try and upgrade to the current stable version (0.21) in which this problem was fixed; we got confirmation from other users that it doesn't crash Firefox like the old one did.

(In reply to avana@hasoft.com from comment #10)

I'm experiencing several crashes a day since updating to 87.0. Each and every crash appears to be instigated by mouse activity inside FF's window. No other application shows this behaviour.

Running:

• Win7 64bit
• FF 87.0
• HTTPS Everywhere
• ImTranslator
• uBlock Origin
• Enhancer for YouTube

This is how it was and never gave me problems. The only changes since the previous FF release that I can recall are going to 87.0 and updated Enhancer for YouTube to 2.0.104.5.

Tried and failed (still crashing):

• FF ESR
• Turned off Enhancer for YouTube
• Used a different HTTPS solution
• Turned off ImTranslator.
• Turned off Hardware Acceleration

I cannot reproduce this at will.

It seems clear that the bug is inside FF. The bug does NOT crash the processor, it locks the screen. The mouse pointer sometimes freezes right away too but sometimes it keeps responding for a couple of seconds. Ctrl+Alt+Del or any other command does not work so we can safely assume the keyboard is locked out also.

Later: 88.0 appears to have solved this issue.

Setting a component for this issue/enhancement in order to get the dev team involved.
If you feel it's an incorrect one please feel free to change it to a more appropriate one.

Madis, do you have an update for us regarding the proposal from comment 13? Thanks!

Hei!

So I've been testin couple of weeks on all three computers and it seems that updating ID software which consists of OpenSC, helped on these cases. Question remains, why isn't error escaped and reported to user? Instead browser fully crashes. I'd reccomend Firefox dev team to implement error correct error handling and this case notify user or disable plugin to avoid crash

Thank you for time and support.

(In reply to Madis from comment #17)

So I've been testin couple of weeks on all three computers and it seems that updating ID software which consists of OpenSC, helped on these cases. Question remains, why isn't error escaped and reported to user? Instead browser fully crashes. I'd reccomend Firefox dev team to implement error correct error handling and this case notify user or disable plugin to avoid crash

Correctly intercepting and reporting these errors turned out to be exceptionally complicated but we made it (see bug 1682507). The new system will be available for all users in Firefox 89 and the work there was motivated among other things by the issues we had with OpenSC.

Given that the problem was with OpenSC installed, shall we make it a dupe of bug 1560486?

The signatures seem not to be the same, I'd propose to close it just WORKSFORME, as the reporter solved their problem.