Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.64.0 OS Version: Linux (Windows might fail too, in the same or in different ways) Follow-up to Steps to Reproduce: See the repo, go to , run for 10-30 minutes
I looked at for issue details. We are facing the same issue in the project. Since the release, running our tests using fails on Windows runner (Windows version 1809) in 100% cases. Every time the mocha runs all tests, they all succeed, but the process finishes with exit code . VS Code version works well. Example CI jobs:
note that I haven't tested on Windows, and it might be a different issue. I suggest attaching a crash report. I got mine by editing our to add .
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from:
I'm not sure how, we currently do this:
See Search for "insider"
Thanks for the logs, crash trace is same as this could only happen if the was never destroyed. Couple of next steps, please test with the insiders as suggested and confirm if the crash repros. In case crash persists, we can add some logging to confirm whether thread safe function was marked for removal We could also refactor the cleanup to rely on instead.
Is this supposed to have been fixed again in between 1.64 and the latest Insiders build? Anyway, it crashed again, after 31 minutes:
The latest insiders from today now contains a fix for the crash caused by a use after free in . I'd appreciate it if you could validate that you're no longer seeing this crash.
Ran without crashing for 1h 17m, I think it's fixed. Thank you! /verified
For what it's worth, the issue is fixed for the project as well. Thank you
Given our green CI history, marking as verified.

Discussion:
"keytar": "7.6.0", "minimist": "^1.2.5", "native-is-elevated": "0.4.3", <del> "native-keymap": "3.1.0", </del> <ins> "native-keymap": "3.2.1", </ins> "native-watchdog": "1.3.0", "node-pty": "0.11.0-beta11", "spdlog": "^0.13.0",

resolved "https://registry.yarnpkg.com/native-is-elevated/-/native-is-elevated-0.4.3.tgz#f1071c4a821acc71d43f36ff8051d3816d832e1c" integrity sha512-bHS3sCoh+raqFGIxmL/plER3eBQ+IEBy4RH/4uahhToZneTvqNKQrL0PgOTtnpL55XjBd3dy0pNtZMkCk0J48g== <del> native-keymap@3.1.0: version "3.1.0" resolved "https://registry.yarnpkg.com/native-keymap/-/native-keymap-3.1.0.tgz#4ad8350f9253d0ae13c77f37d4a34ab4773e305f" integrity sha512-h67B9n/L0DRGAftZqO7ZTlgGy7UY8r7N/GOAnnDibmRqFoenjbd9IdkN9uCf1Xs+vGW4BDJn9ZtO6xwJAbDmEA== </del> <ins> native-keymap@3.2.1: version "3.2.1" resolved "https://registry.yarnpkg.com/native-keymap/-/native-keymap-3.2.1.tgz#2b34ee7e08722f107baba9beae7e61ea43eceae7" integrity sha512-kR8r1Ody16qNE52fenuCMQBHtFpIV7HNVjQA7dm/pXpFcQmqCl8jWQuJYdZvNH7fQmyAv3lOgPfR3FDHPRYiiA== </ins> native-watchdog@1.3.0: version "1.3.0"