Change:
logService.trace('getUnixShellEnvironment#noAttach', noAttach); const mark = generateUuid().replace(/-/g, '').substr(0, 12); <del> const regex = new RegExp(mark + '(.*)' + mark); </del> <ins> const regex = new RegExp(mark + '({.*})' + mark); </ins> const env = { ...process.env,

Discussion:
<!-- 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.66.2 OS Version: Ubuntu Studio Xfce4 Linux x64 5.13.0-19-lowlatensy Steps to Reproduce: to next line: VS Code from the Applications Menu or double click the associated file error message: ! Upd: If I comment this line VS Code runs without error.
Do you see any errors in you for User and Workspace?
no, I don't see any error in my .
What are you trying to do with that line?
this line changes the title of my terminal window to the currently running command, so that I can see in the taskbar which command currently running in each terminal window. but it shouldn't matter to . and a few versions ago it was. I have been using this line since very beginning of using Linux. and didn't throw this error until recently.
I that line to my and I don't see that error when VS Code launches, we source a "dev environment" by running your default shell. When this fails we show the error message that your shell returned. You have some issue in your shell init files that's causing that error, you need to investigate on your end as it's a problem with your environment, not with VS Code. See here for what we do before showing this error:
I'd disagree with this being an environment problem and I'm not sure if should be closed.

Unable to resolve your shell environment: Unexpected number in JSON at position 35 I'm seeing the exact same problem as the OP in 1.68.0 (can't say when it started, skipped a few versions) and it's triggering over a custom git prompt in bash on Ubuntu that I've been using fine in all sorts of environments since forever. Happy to provide more info to debug this if that helps and if you'd provide some guidance what to do. Also: if there is an issue in a user's shell configuration, wouldn't it be useful to make the error message a bit more user friendly? As a suggestion, it'd be good if it explained that and maybe render the actual command VS Code tried to run and that failed? Or some more information in VS Code logs?
This is a better repro for me from To repro in code-oss, add that to .bashrc and run (or debug Main Process target) after commenting out this line:
The exception happens here: '" + JSON.stringify() + ""'{"key":"value",...}' This is what rawStripped is: <img width="622" alt="Screenshot 2022-12-02 at 10 19 27 am" src="https://user-"Here's what it is when it works:
And the raw when it doesn't work: <img width="1141" alt="Screenshot 2022-12-02 at 10 23 34 am" src="https://user-"The 2 marks are in the sequence, we should be matching on the last 2 marks, not the first 2.