VS Code crashes with error 132
See original GitHub issueDoes this issue occur when all extensions are disabled?: No
- VS Code Version: 1.63.2
- OS Version: Ubuntu 18.4
Steps to Reproduce:
- Start code with extension ‘ViDE-Software.v4pvhdlforprofessionals’ installed
- Open a file with extension .vhd to activate the extension
- Wait a couple of seconds, VS Code shows a window “The window has crashed. Reason: ‘crashed’ code: 132”
I could already narrow it down to some settings in the package.json of the extension (of which I am the author). There is a similar issue where I already described the behavior: #130375, but it has been closed by the bot.
Please refer to this message for details: https://github.com/microsoft/vscode/issues/130375#issuecomment-922007487
Please find attached an crash-dump.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Error 132 - Blizzard Support - Battle.net
Error 132 is a generic error code that may be caused by out-of-date addons, corrupted files, incompatible drivers, or hardware issues.
Read more >VSCode crashes when starting up in Ubuntu - Stack Overflow
The vscode was installed by apt. And it could be open for a few seconds, then it crashes automatically. I tried to figure...
Read more >Error 132 when playing World of Warcraft - Microsoft Community
It could be 20 mins to an hour or more. The following errors are showing up in windows leading up to the crash....
Read more >[Solved] World of Warcraft Error 132 Fatal Exception
A missing or outdated video card driver can cause the error 132 in WOW, so you should update your graphics card driver to...
Read more >Error #132 - Technical Support - World of Warcraft Forums
this application has encountered a critical error error #132 (0x85100084) fatal exception! ... Make sure you have any overlays turned completely ...
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 Free
Top 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
Thanks for the minimal repro, can confirm the issue on my end.
May I ask if it is planned to fix this issue? While I understand that it is not critical, it is quite annoying nonetheless. Thanks for your support!