One thing that came out of the content process rename (bug 1114647) was that some AV software was regarding the new process name as suspicious and quarantining us. I don't *think* this is going to be an issue for the GPU process as we now use firefox.exe for it, but we should do testing like we did in bug 1114647 anyway.
Ryan, since you sorted out the QA for this last time round, is it possible you could get someone to look at this? The pref that needs switching would be layers.gpu-process.dev.enabled.
Flags: needinfo?(ryanvm) → needinfo?(rares.bologa)
Hi, I have just finished to test this with different antivirus clients on Windows 10 x64 and I have not encountered any conflicts or anything suspicious between the new process and the installed AV clients. The browser starts and works without any problems. For testing this I have used the Nightly build from 2016-10-30 with 32 bit and also with 64 bit. Manually added the boolean "layers.gpu-process.dev.enabled" pref and set it to true. While testing I followed the firefox processes from Task Manager when navigating on different websites (eg: YouTube, Facebook, Vimeo, http://www.sensisoft.com/ and http://www.gamesgames.com/). This are the AV clients used for testing: 1. Avast Free Antivirus - No conflicts 2. Eset Nod 32 Antivirus Trial - No conflicts 3. AVG - No conflicts 4. Panda Antivirus Pro Trial - No conflicts 5. Avira Free - No conflicts 6. Norton Security Premium Trial - No conflicts 7. Mcafee - No Conflicts 8. Kaspersky Endpoint Security 10 - No conflicts 9. Bitdefender Free Edition - No Conflicts I will continue to run the same tests on Windows 8.1 x32 and Windows 7 x64 with the same AV clients and return with the results found.
I have finished testing this on Windows 7 x64 and Windows 8.1 x64, using the same scenarios and AV clients as I described in comment 2. I have not encountered any issues or conflicts between the new process and the installed AV clients. Please let me now if you want to test on different OSs or AV clients.
I believe that should be sufficient. Thanks for this!
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.