VSCode Version:
_Version: 1.36.1
Commit: 2213894ea0415ee8c85c5eea0d0ff81ecc191529
Date: 2019-07-08T22:55:08.091Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 5.0.9-050009-generic_
OS Version:
_Ubuntu 16.04_
Firefox version:
_68.0_
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
I'm a bit puzzled by this one, because what does Firefox have to do with Code? But it's 100% reproducible.
The Firefox _PROFILE/crashes/events_ directory is empty and I'm looking for a way to provide more information.
Hi, I've also faced the same error and was about to create a Bug Report when I found it already created.
@deepak1556 ever heard this?
@bpasero I've just downloaded the exploration build DEB and tested the same. I'm afraid but the issue is still there. I'm attaching two screenshots to maybe help you in any way possible. Thank you.



Thanks for testing :+1:
@bpasero @deepak1556 Just to make sure that the issue is not with Electron, I've just installed Atom editor and tested the same, it did not happen to crash my Firefox. So, we're sure that the issue is somewhere in VSCode's source code.
@tusharsrivastava that depends. Atom might be using a very different Electron version from VSCode. Are you sure Atom is using Electron 4?
@bpasero I checked, Atom is using Electron 3.1.10
@tusharsrivastava so would you agree this could be due to the change in Electron versions?
@bpasero I'm still not sure. Seems like Electron's issue but I guess we need more information here. Also, I'm not sure if a simple "Hello World" application in Electron 4+ can reproduce this bug?
@tusharsrivastava yeah give it a try
@bpasero I did the testing and sure enough, the bug is in electron's version. I ran the hello world application and it surely did crashed my firefox. What should we do next?
@bpasero Moreover, I've just tested by launching google chrome and interestingly the issue probably is with Chrome/Chromium as electron's using the same and my firefox crashed again.



@tusharsrivastava great, I suggest to report it over at https://github.com/atom/electron
I'm facing the same issue and noticed this bug was also reported on the Mozilla bug tracker:
https://bugzilla.mozilla.org/show_bug.cgi?id=1566053
EDIT: And I've opened an issue over at Electron now, like @bpasero suggested: https://github.com/electron/electron/issues/19694
@pmoris I've also faced the same issue when opening Google Chrome or Chromium. I guess the issue is rooted somewhere in chrome base.
Most helpful comment
@bpasero I've just downloaded the exploration build DEB and tested the same. I'm afraid but the issue is still there. I'm attaching two screenshots to maybe help you in any way possible. Thank you.