A few times per day, my local SST debug sessions c...
# sst
d
A few times per day, my local SST debug sessions crash. Does anyone else have this problem?
Copy code
fatal error: all goroutines are asleep - deadlock!

goroutine 1 [semacquire]:
sync.runtime_Semacquire(0x0)
        runtime/sema.go:56 +0x25
sync.(*WaitGroup).Wait(0xc00000e010)
        sync/waitgroup.go:130 +0x71
main.runService(0x1)
        <http://github.com/evanw/esbuild/cmd/esbuild/service.go:138|github.com/evanw/esbuild/cmd/esbuild/service.go:138> +0x4cb
main.main()
        <http://github.com/evanw/esbuild/cmd/esbuild/main.go:200|github.com/evanw/esbuild/cmd/esbuild/main.go:200> +0x1eb

goroutine 4 [chan receive]:
main.runService.func1()
        <http://github.com/evanw/esbuild/cmd/esbuild/service.go:66|github.com/evanw/esbuild/cmd/esbuild/service.go:66> +0x4b
created by main.runService
        <http://github.com/evanw/esbuild/cmd/esbuild/service.go:64|github.com/evanw/esbuild/cmd/esbuild/service.go:64> +0x212

goroutine 5 [chan receive]:
main.(*serviceType).sendRequest(0xc000064190, {0x13f20a0, 0xc032732690})
        <http://github.com/evanw/esbuild/cmd/esbuild/service.go:163|github.com/evanw/esbuild/cmd/esbuild/service.go:163> +0xda
main.runService.func2()
        <http://github.com/evanw/esbuild/cmd/esbuild/service.go:92|github.com/evanw/esbuild/cmd/esbuild/service.go:92> +0x39
created by main.runService
        <http://github.com/evanw/esbuild/cmd/esbuild/service.go:89|github.com/evanw/esbuild/cmd/esbuild/service.go:89> +0x313
t
Haven't seen this, seems like a long running esbuild thing
f
@David Martin btw are you on Windows?
d
osx
if it’s a long-running build, then it’s likely related to my machine
t
I think we keep the esbuild instance around to do rebuilds
Seems like there's some issue with that but I haven't personally seen it
d
ok. let’s punt on it for now. if it’s still a problem once i get a new mac, then it’ll make sense to dig further.
f
Came across this https://github.com/evanw/esbuild/issues/646 can you try setting the GODEBUG environment for ur start script ie.
GODEBUG=asyncpreemptoff=1 sst start
asyncpreemptoff
seems to be a windows flag.. but maybe give it a try?
d
ok, added it. i am starting the debug process from VSCode and I didn’t modify the launch.json, but i think it calls that the start script anyway
i’ll let you know how it goes, but when it crashes again is unknown
f
Sounds good!