Open Bug 1451260 Opened Last year Updated 2 months ago

Firefox fails to launch with the latest Kaspersky (G) patch

Categories

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

All
Windows
defect
Not set
critical

Tracking

(firefox-esr52- wontfix, firefox-esr60 unaffected, firefox59 wontfix, firefox60- wontfix, firefox61 unaffected)

Tracking Status
firefox-esr52 - wontfix
firefox-esr60 --- unaffected
firefox59 --- wontfix
firefox60 - wontfix
firefox61 --- unaffected

People

(Reporter: emilghitta, Unassigned)

References

Details

(Keywords: qablocker)

Attachments

(1 file)

[Tracking Requested - why for this release]:
Kaspersky related issue affecting the startup of Fx beta, release and esr.

[Affected versions]:
Firefox 60.0b9 (BuildId:20180402175344).
Firefox 59.0.2 (BuildId:20180323154952).
Firefox 52.7.3 esr (BuildId:20180322140748).

[Unaffected versions]:
Firefox 61.0a1 (BuildId:20180403220040).

[Affected platforms]:
Windows 10 64bit.

[Preconditions]
You need to install any of the following Kaspersky free trials:
Kaspersky Anti- Virus -https://www.kaspersky.ro/download/antivirus
Kaspersky Internet Security - https://www.kaspersky.ro/download/internet-security
Kaspersky Total Security - https://www.kaspersky.ro/download/total-security 
 
You need to install the latest patch (G) by performing the following steps:
1. Run the Database update of Kaspersky.
2. Restart the computer when the update is completed.

[Steps to reproduce]:
1.Try launching Firefox executable.

[Expected result]:
Firefox successfully launches.

[Actual result]:
Firefox does not launch.

[Additional information]:
For further information regarding this issue please observe the following screencast: https://drive.google.com/open?id=15c3yf1eaTpEFAxUDiEL51M82lD3HS9FU

It seems that no crash report is generated.

This issue is not reproducible with Firefox latest Nightly.
Can you try forcing a Firefox crash? https://developer.mozilla.org/en-US/docs/Mozilla/How_to_report_a_hung_Firefox
This might allow us to see where it is blocked.
Flags: needinfo?(emil.ghitta)
Attached image kaspersky-issue.gif
I tried forcing Firefox to crash using  the steps from comment 0 and from comment 1, but after further investigation, I noticed that the Firefox process is not displayed inside task manager once you run the fx executable. It seems that every time you try running the Firefox executable another process called "ffcert.exe" gets called. If the ffcert.exe process is killed from the task manager, Firefox seems to start afterwards. For further details I have attached a screencast.
Flags: needinfo?(emil.ghitta)
Hey Alexey, could this be somehow related to bug 1449115?
Flags: needinfo?(alexey.totmakov)
(In reply to Marco Castelluccio [:marco] from comment #3)
> Hey Alexey, could this be somehow related to bug 1449115?

Marco, the problems bug 1449115 and bug 1451260 does not looks connected. 
In this case (bug 1451260) i see some incompatibles in using NSS API by ffcert.exe and implementation of NSS API in Firefox 60.0b9, 59.0.2, 52.7.3.

I will try to describe the scenario. Kaspersky pause Firefox start, enumerating Firefox storage with NSS API, and if it is necessary, install Kaspersky's certificate to Firefox storage. Then Firefox start resumed.
 
Probably in this case, some calls to NSS API are hang. To reverse the problem we need a dump of ffcert.exe process, after it hangs. Alternatively, maybe some of Firefox developers will inspect ffcert.exe codebase, for check if we use NSS API in correct way. We are ready for cooperation in ffcert development.
Flags: needinfo?(alexey.totmakov)
Hi Alexey, I've generated a dump file for ffcert.exe process. Also I made a screenshot of an error that was thrown by the antivirus after launching firefox and killing the ffcert.exe process, with Kaspersky freshly installed, maybe it has some valuable information.

Here is the link with the two: https://drive.google.com/drive/folders/1xs4g7kmr29ksMcKW7F4ha71sKy3Wuxw-
see comment 5
Flags: needinfo?(alexey.totmakov)
Casca, thanks a lot for the dump!

There is a bug in Kaspersky product. Sometimes, we can block Firefox start. These conditions must be met for reproduction – size of traces in ffcert should be multiple of buffers size on Windows named pipes.
Unfortunately, there is no stable workaround :( However, judging by Kaspersky support, the problem is not affects many users. What do you think about importance of the problem? How many users report about this problem?

By the current plan, we have two options to fix the scenario.
1. Patch for KIS2018 will be available in the middle of June.
2. New release of KIS2019 we be available for Europe to end of May. Global release of KIS2019 will be available to the end of July.
What do you think about these dates? Is it acceptable for you?
Flags: needinfo?(alexey.totmakov)
(In reply to Alexey Totmakov from comment #7)
> Casca, thanks a lot for the dump!
> 
> There is a bug in Kaspersky product. Sometimes, we can block Firefox start.
> These conditions must be met for reproduction – size of traces in ffcert
> should be multiple of buffers size on Windows named pipes.
> Unfortunately, there is no stable workaround :( However, judging by
> Kaspersky support, the problem is not affects many users. What do you think
> about importance of the problem? How many users report about this problem?

It looks like several people from our QA can reproduce this problem. Not sure about the general population.

> 
> By the current plan, we have two options to fix the scenario.
> 1. Patch for KIS2018 will be available in the middle of June.
> 2. New release of KIS2019 we be available for Europe to end of May. Global
> release of KIS2019 will be available to the end of July.
> What do you think about these dates? Is it acceptable for you?

Do you think a workaround instead of a full fix could be implemented a bit more quickly?
(In reply to Marco Castelluccio [:marco] from comment #8)

> Do you think a workaround instead of a full fix could be implemented a bit
> more quickly?

For patch to KIS2018 I do not see any option to release fix earlier than June.

For KIS2019 it is possible to check fix on RC build - https://forum.kaspersky.com/index.php?/topic/389678-kfakavkisktsksksos-19001088-rc/
direct link 1 - https://box.kaspersky.com/d/17f0c6e16b6e4e009ca6/
direct link 2 - https://cloud.qainfo.ru/s/FcCXZ7OY3d1WGGQ
Too late to fix this in 59.
Sasca, could you verify the issue no longer reproduces with the RC build Alexey gave us in comment 9?
Flags: needinfo?(catalin.sasca)
I can confirm that this issue is not reproducible on Firefox 60.0RC and Firefox 60.0b16 while using the KIS 19.0.0.1088RS build that Alexey provided in Comment 9.
Flags: needinfo?(catalin.sasca)
Flags: needinfo?(aldenmichael002)

Look for antivirus problem too it may be cause for your Mozilla.

You need to log in before you can comment on or make changes to this bug.