In VSCode, after running

sst start

for a few minutes and a few rebuilds from code changes on a TypeScript project, the debugger stops hitting breakpoints. Looking at dev tools in VSCode I see the error

Error: Error processing setBreakpoints: RangeError: Start offset -2140284536 is outside the bounds of the buffer

Looking at the Github issues for VSCode I came across this which suggests it's to do with invalid sourcemaps. Could something to do with the sourcemaps be getting corrupted following a rebuild of the code?

Hey @Ross Coundon did this start happening after a recent update?

It's hard to say, I've had issues a number of times with VSCode where the extension host crashes while debugging in SST over the last couple of months. When that happens the breakpoints are no longer hit when debugging. Over the last few days I've started pulling up the VSCode dev tools to try to understand why. I went through the extension bisect process but that didn't reveal anything. Looking at dev tools when this happens shows various different outputs of which this was one which seems to be do with source maps. (I've seen others such as Out of Memory and some that have literally no hits when googling) Unfortunately, I can't say whether the previous problems I experienced were related to this or something else.

Hm the only change to sourcemaps was I put them inline instead of a separate file - let me play with putting them in both

@Ross Coundon just checking in, r u still having this issue?

I've actually switched to using WebStorm now and I've not seen it there, also, the debugger seems much more stable. This is possibly because it's possible (and simple) to adjust the memory allocation.