Describe the bug
A clear and concise description of what the bug is.

I have launch.json config like this

		{
			"name": "Launch Extension",
			"type": "extensionHost",
			"request": "launch",
			"args": [
				"--extensionDevelopmentPath=${workspaceFolder}/out-src",
			],
			"sourceMaps": true,		
			"pauseForSourceMap": true,	
			"outFiles": [
				"${workspaceFolder}/out-test/**/*.js",
				"${workspaceFolder}/out-src/**/*.js",
				"${workspaceFolder}/../common/out-*/**/*.js",
			],
		},

when I run it second instance of vscode starts right away, but breakpoints do not get hit in there initially (they are shown as not being resolved) and the whole extension host is sluggish (does not even react to stop button). Profiling the extension host shows it is in some vscode-js-debug code dealing with source maps:

I tried running multiple times and it is always somewhere in the getCompiledLocations method

To Reproduce

I can't provide small repro example, it only happens with our real extension that I can't share. If it makes any difference it is bundled by esbuild, the js bundle is 4.8MB and the associated source map is 3.4MB

Log File

sent via email

VS Code Version: tried in 1.96.4, 1.100.2 and 1.103.1