"fatal error: unexpected signal during runtime execution"

Support
1

I’ve just found this panic log from ~2 weeks ago. The panic seems to have happened only once, as otherwise Syncthing does run fine on the device. This is an old laptop running Windows 8.1 x64.

The culprit may as well be a hardware issue, since the laptop does experience some overheating problems. Still, I’m posting this just in case it is something else.

Please have a look at the log when you’ve got some free time.

fatal error: unexpected signal during runtime execution
[signal 0xc0000005 code=0x0 addr=0xffffffffffffffff pc=0x423832]

goroutine 3 [running]:
runtime.throw({0xee20f9, 0x0})
	runtime/panic.go:1198 +0x76 fp=0xc000055ef8 sp=0xc000055ec8 pc=0x439076
runtime.sigpanic()
	runtime/signal_windows.go:248 +0x22b fp=0xc000055f40 sp=0xc000055ef8 pc=0x44d7cb
runtime.(*mSpanStateBox).get(...)
	runtime/mheap.go:372
runtime.sweepone()
	runtime/mgcsweep.go:277 +0x72 fp=0xc000055fb0 sp=0xc000055f40 pc=0x423832
runtime.bgsweep()
	runtime/mgcsweep.go:166 +0x105 fp=0xc000055fe0 sp=0xc000055fb0 pc=0x423785
runtime.goexit()
	runtime/asm_amd64.s:1581 +0x1 fp=0xc000055fe8 sp=0xc000055fe0 pc=0x46a6e1
created by runtime.gcenable
	runtime/mgc.go:181 +0x55

panic-20220108-154150.log (511.0 KB)

2

Suggest you google that error. Its a go runtime error. Could be a badly built binary.

3

Yeah, I did, but I couldn’t find anything conclusive (or at least not something that I could process with my limited skills). The binary itself is fine though - the exact same one has been used on a dozen of different systems with no issues.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.