1495114 - Users report Firefox 64 is no longer opening/starting up when CbDefense is installed

Status: NEW

(External Software Affecting Firefox :: Other, defect, P2)

Description

[[:philipp]]

there are a few users reporting in support channels today that the recent Nightly is no longer starting up properly.

the most detailed information is available in the thread https://support.mozilla.org/en-US/questions/1235552 where an affected user has narrowed down the issue to the changes landing via bug 1488554 and is suspecting his CbDefender security software to interfere.

other reports so far:
https://support.mozilla.org/en-US/questions/1235528
https://old.reddit.com/r/firefox/comments/9jgoxj/firefox_nighty_will_not_open/

Comment 1

[(No longer employed by Mozilla) Aaron Klotz]

Since we have confirmation that CbDefender is the problematic third-party software, I'm going to re-purpose this bug specifically for that case. Let's file new bugs as we discover any new third-party products that are not working well with the launcher process.

Comment 2

[copyliu]

I can reproduce with Dr.Web installed. firefox.exe killed immediately.

mozregression logged:
Assertion failure: false (MOZ_ASSERT_UNREACHABLE: Unrecognized opcode sequence), at z:/build/build/src/obj-firefox/dist/include/mozilla/interceptor/PatcherDetour.h:950

Comment 3

[nayinain]

I can also reproduce the issue with Huorong installed.

Comment 4

[(No longer employed by Mozilla) Aaron Klotz]

Please file each third-party product as its own bug.

Comment 5

[Rares Doghi, Desktop QA]

Hi, I am unable to check this issue since we don't have any license for this specific Antivirus and there seems to be no trial version available, can someone please confirm if this issue is fixed in the latest Nightly Build ?

Comment 6

[(No longer employed by Mozilla) Aaron Klotz]

I would like to leave this open, because essentially the way this is "fixed" in Nightly is for the launcher process to disable itself. If you check your about:support, you will probably find the Launcher Process state set to "Disabled due to failure". In the long term, we would like to fix that, but for the purposes of release on 67, this is exactly what we want to see.