Launcher doesn't kill Firefox 68
See original GitHub issueFirefox : v68.0.1 OS : Window7 and Windows 10 Karma : v1.7.1 || v3.1.4 || 4.2.0 Firefox launcher : v1.1.0 Node.js : v8 || v10
Launcher doesn’t kill my Firefox 68, I tested with several version of nodejs without success. Maybe it’s cause of Electrolyse (e10s) maybe not. I tried to disable e10s for a moment with set MOZ_FORCE_DISABLE_E10S variable but unsuccessful, I created a little standalone code to test.
const spawn = require('child_process').spawn;
let firefox = spawn("pathToFirefox\\firefox.exe, [
"http://localhost:9876/?id=anid",
"-profile",
"C:\\temp\karma-2456",
"-no-remote",
"-wait-for-browser"
]);
setTimeout(function killFirefox(){
firefox.kill();
}, 10000)
firefox.on('exit', function(code, signal){
console.log('Firefox exit');
});
Result: firefox is always running.
I tried with this version How to kill child processes that spawn their own child processes in Node.js but it doesn’t work for me.
has anybody an idea ?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:20 (4 by maintainers)
Top Results From Across the Web
Firefox froze on the update to 68.0 and I cannot reinstall it.
Hi pattyfingers, one of the changes in Firefox 68 is a new launcher process. Perhaps it would be worth trying to disable that...
Read more >Firefox upgraded to 68 I can't save anything to C:\ "A ...
Firefox 68 introduces a new launcher process that reduces the browser to running as a standard user (medium integrity).
Read more >Drag and Drop errors with Firefox Launcher Process ...
How to fix Firefox drag-and-drop errors when running Windows as Administrator with UAC disabled and the Launcher Process enabled.
Read more >1529593 - Launcher Process - Disabled due to failure in ...
You're going to need to do some troubleshooting. Start Firefox with the following command line options: ... Once you have checked about:support and...
Read more >Security vulnerabilities fixed in Firefox 68
Description. When an inner window is reused, it does not consider the use of document.domain for cross-origin protections. If pages on ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dotnetCarpenter It looks like the fix for this is finally released!
Switching to Nightly (70.0) I can reproduce the problem and the changes in the
kill-browser-process
branch seem to fix it for me. If someone else can confirm that would be helpful.I suspect what was happening with 69 is I triggered an error condition where the launcher process was disabled.
Unfortunately I still don’t have a good idea how to fix WSL.