vscode-firefox-debug
vscode-firefox-debug copied to clipboard
Debugging breaks sound output
Description
When debugging an application with the Firefox debugger, the sound output of my pc gets weird as soon as I hit a breakpoint and hover over a variable in VSCode (to view its value).
What happens to the sound:
- it's distorted
- random noise
- there's an echo ~1s later
This problem appears since I've upgraded to VSCode 1.47.0 (though I don't use it often while playing music, so the problem could have started sooner).
Environment
- VSCode Version: 1.47.0
- OS Version: Fedora 31
Steps to Reproduce
- turn on some music
- Add breakpoint
- Run app and debugger
- trigger breakpoint
- go into vs code and hover over a variable / parameter to see the value popup
- notice that the music just got buggy
Additional information
I've noticed that the following new devices appear in the sound settings

Can confirm having this issue too.
In launch mode, audio in videos are not working at all. Not in my dev-site or in others, like video-sites.
In attach mode, the audio is stuttering, and sounds like an echo effect, but worse.
VS Code: 1.47.1 Node: 12.8.1 Using Firefox 78.0.2 (64-bit) (using latest snap) on Ubuntu 20.04 LTS. Computer: (AMD) Acer Aspire V5 552 (will try it on a newer computer too when I get it back from service)
I had the same issue sporadically in the past (also on Linux). If I remember correctly it also happened when I was using Firefox' built-in debugger, so I wrote it off as an upstream issue. Could you try if this also happens for you in Firefox' built-in debugger?
Could you try if this also happens for you in Firefox' built-in debugger?
It doesn't happen in the built-in debugger for me.
@LorenzHenk
Could you try if this also happens for you in Firefox' built-in debugger?
It doesn't happen in the built-in debugger for me.
Did you start Firefox with the --start-debugger-server option? (Because that is what is needed tobe able to remote debug.)
It could be a bug in Firefox's functionality also, which sounds more logical, because it needs to do more work as usual. Normal use of the build-in debugger only affects the current page, while the option affects the whole Firefox instance if i'm not wrong.