runtime.asmstdcall()

[terry]

Had this started to appear on different PCs (1.27.1 rc1)…

[NAGDY] 2023/12/08 20:19:19 INFO: TCP listener ([::]:22000) shutting down

[NAGDY] 2023/12/08 20:19:19 INFO: Exiting

Exception 0xc0000005 0x8 0x0 0x0

PC=0x0 runtime.asmstdcall()

runtime/sys_windows_amd64.s:65 +0x75 fp=0x22fca0 sp=0x22fc80 pc=0x473dd5

rax 0x0

rbx 0x1a27f20

rcx 0x1a88240

rdi 0x7fffffdd000

rsi 0x22fea0

rbp 0x22fde0

rsp 0x22fc78

r8 0x0

r9 0x22fee0

r10 0x1a59a38

r11 0x21

r12 0x22fec0

r13 0x1

r14 0x1a27480

r15 0x0

rip 0x0

rflags 0x10293

cs 0x33

fs 0x53

gs 0x2b

Exception 0xc0000005 0x8 0x0 0x0

[calmh (Jakob Borg)]

Full trace might help, possibly, but I’m inclined to suspect things like antivirus…

[terry]

It’s up to four this morning. Only one has anti virus, windows defender. The rest are on old servers.

Don’t know if it helps, but it seems to be on devices that are based on Windows 7 / Server 2008r2 (all backup servers, not production). So wonder if it’s calling a dll that’s no longer supported. I checked a W11 St and that was fine

[tomasz86]

For the record, Go dropped Windows 7 support in 1.21.

Go 1.20 is the last release that will run on any release of Windows 7, 8, Server 2008 and Server 2012. Go 1.21 will require at least Windows 10 or Server 2016.

Source: https://tip.golang.org/doc/go1.20

[terry]

I suspected this will be the case, I just rolled all the devices back to 1.27 and they are fine. Unfortunately i’m stuck with these older ones, mainly because they are repurposed machines and only have the one job, to read only network files and sync them to me.