I use WSL2 with Ubuntu 20.04 for development. Steps to reproduce: 1) Do a full local build of Firefox 2) Execute `./mach run` 3) Open the browser toolbox (`ctrl-shift-alt-i`) 4) Close the dev build of Firefox Expected behavior: After closing the dev build of Firefox, the browser toolbox window should close simultaneously. Actual behavior: The dev build of Firefox is now closed, but the corresponding browser toolbox window remains open. A large number of errors appear in the terminal. I've attached a file with the full terminal output from taking the following steps: 1) `./mach run` (right after doing a full build) 2) Opening the browser toolbox via the keyboard shortcut (`ctrl-shift-alt-i`) 3) Clicking the 'X' in the top right corner of my Firefox dev build to close the application 4) Clicking the 'X' in the top right corner of my browser toolbox to end the debugging session.
Bug 1770527 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I use WSL2 with Ubuntu 20.04 for development. Steps to reproduce: 1) Do a full local build of Firefox 2) Execute `./mach run` 3) Open the browser toolbox (`ctrl-shift-alt-i`) 4) Close the dev build of Firefox Expected behavior: After closing the dev build of Firefox, the browser toolbox window should close simultaneously. Actual behavior: The dev build of Firefox is now closed, but the corresponding browser toolbox window remains open. A large number of errors appear in the terminal. I've attached a file with the full terminal output from taking the following steps: 1) `./mach run` (right after doing a full build) 2) Opening the browser toolbox via the keyboard shortcut (`ctrl-shift-alt-i`) 3) Clicking the 'X' in the top right corner of my Firefox dev build to close the application 4) Clicking the 'X' in the top right corner of my browser toolbox to end the debugging session. Further info: A teammate of mine was not able to reproduce this bug on MacOS. He then tried to reproduce the bug on a Linux VM and initially couldn't. But he was using a build that was a few months old. When he refreshed the tree and rebuilt, he was able to reproduce the bug on Linux.