Closed Bug 1397750 Opened 3 years ago Closed 28 days ago
Startup crash in Abort | new XPCJSContext failed to initialize
. | mozalloc _abort (Quick Heal Antivirus DLL)
This bug was filed from the Socorro interface and is report bp-30034b90-73fd-4c3e-84c5-c1e810170907. ============================================================= Crashing Thread (0) Frame Module Signature Source 0 mozglue.dll mozalloc_abort(char const* const) memory/mozalloc/mozalloc_abort.cpp:33 these crashes during startup spike up in 56.0b9 with ###!!! ABORT: new XPCJSContext failed to initialize.: file z:/build/build/src/js/xpconnect/src/XPCJSContext.cpp, line 954 the signature is currently accounting for 1% of browser crashes in 56.0b9. there are no correlations available for it yet, but a manual spot check in a couple of different reports always turned up the presence of the module ScDetour.Dll v188.8.131.52 which apparently belongs to Quick Heal AntiVirus (FileDescription: Browser Sandbox Interceptor Module).
Another high volume startup crash. I'll email QuickHeal about this one as well.
This crash affects both 32- and 64-bit Firefox users.
Hardware: All → x86_64
Summary: Startup crash in Abort | new XPCJSContext failed to initialize. | mozalloc_abort → Startup crash in Abort | new XPCJSContext failed to initialize. | mozalloc_abort (Quick Heal Antivirus DLL)
From email with QuickHeal engineers, they are going to deploy a fix in their product around Sept. 20th.
We are still seeing a few crashes in 56 beta 12, but nothing past that. Keeping this open so we will be sure to monitor the crash rate after 56 release/ 64-bit migration.
I'm unblocking the Win64 migration meta bug 1274659 because this Quick Heal crash affects 32- and 64-bit Firefox equally 50/50%.
No longer blocks: win64-migration
This isn't high volume enough to warrant a dot release, wontfix for 56. I think the crash rate here looked high on beta because of the differences in our beta and release populations.
Status: NEW → RESOLVED
Closed: 28 days ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.