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.91.0-insider OS Version: MacOS 11 Steps to Reproduce: running tests on macos 11 e.g.
90.0 still works if needed
Can you collect crash dump from the pipeline following the steps at , thanks!
The only available file was generated in the subdirectory The job is , an extra warning message was generated
Symbolicated trace
Crash at following due to incorrect value types, I don't see any recent changes along the crash code path that would explain this. We are pretty much calling into N-API in . A next good step would be to bisect the change, I can only try this next week . If possible, can you help narrow down the commit that introduced the regression ? You can pass commit value to the field of api, ex:
I modified the job definition so it can be started with arbitrary commit, but I have to wait for the macos11 brownout to be over to run the test.
I am also seeing this same crash on
This is the crash dump from commit :
I managed to narrow the commit range to - still works - no longer works This commit is the one that stands out...
This works. Make sure to turn off auto updates as well. This morning, I was confused on why VS Code broke again.
same here 1.91.0-insider on mac os 11.7.10 (20G1427) crashing as soon as started rolling back to 1.90.0
It fails on VsCode insiders. Here's the stack trace:
This seems to have just started happening on the regular release version of VSCode too, as of 1.91.0[^1]. Downgrading to 1.90.2 works for now ([Universal][], [Intel][], [Apple Silicon][]) - just remember to [turn off updates][] for now, as mentioned in [^1]: Only tested on macOS 10.15.7 Catalina so far, but it seems to be the exact same crash the Insiders version was getting on both 10.15 Catalina and 11 Big Sur. [Universal]: [Intel]: [Apple Silicon]: [turn off updates]:
Yes, I also have the same problem now on stable with macOS 11.7.10. Thanks for all the links , downgrade helped.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
/verified

Discussion:
<del> 2024-05-25T03:29:59.419Z </del> <ins> 2024-07-04T16:31:11.121Z </ins>

- script: | set -e <ins> # Refs https://github.com/microsoft/vscode/issues/219893#issuecomment-2209313109 sudo xcode-select --switch /Applications/Xcode_15.2.app condition: and(succeeded(), ne(variables.NODE_MODULES_RESTORED, 'true')) displayName: Switch to Xcode >= 15.1 - script: | set -e c++ --version </ins> python3 -m pip install setuptools for i in {1..5}; do # try 5 times