What is the issue?
After 24 hours of usage, the binary of the architecture mipsle fails like this:
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x2 addr=0x6fe72000 pc=0x2889c]
goroutine 1 [running, locked to thread]:
runtime.throw({0x8ae889, 0x2a})
runtime/panic.go:1198 +0x60 fp=0x14689c8 sp=0x14689b4 pc=0x5499c
runtime.sigpanic()
runtime/signal_unix.go:719 +0x308 fp=0x14689e0 sp=0x14689c8 pc=0x73080
runtime.heapBitsSetType(0x1474180, 0x18, 0x18, 0x804800)
runtime/mbitmap.go:1278 +0x8b4 fp=0x1468a44 sp=0x14689e4 pc=0x2889c
runtime.mallocgc(0x18, 0x804800, 0x1)
runtime/malloc.go:1100 +0x8ac fp=0x1468a88 sp=0x1468a44 pc=0x1e314
runtime.convT2E(0x804800, 0x1468b1c)
runtime/iface.go:325 +0x4c fp=0x1468aa0 sp=0x1468a88 pc=0x1b0fc
encoding/xml.init()
encoding/xml/read.go:301 +0x1f4 fp=0x1468b34 sp=0x1468aa0 pc=0x3cb01c
runtime.doInit(0xcf5520)
runtime/proc.go:6501 +0x1a0 fp=0x1468c58 sp=0x1468b34 pc=0x69bb4
runtime.doInit(0xcf5820)
runtime/proc.go:6478 +0x94 fp=0x1468d7c sp=0x1468c58 pc=0x69aa8
runtime.doInit(0xcf7ba0)
runtime/proc.go:6478 +0x94 fp=0x1468ea0 sp=0x1468d7c pc=0x69aa8
runtime.doInit(0xcf9f00)
runtime/proc.go:6478 +0x94 fp=0x1468fc4 sp=0x1468ea0 pc=0x69aa8
runtime.main()
runtime/proc.go:238 +0x268 fp=0x1468fec sp=0x1468fc4 pc=0x58440
runtime.goexit()
runtime/asm_mipsx.s:625 +0x4 fp=0x1468fec sp=0x1468fec pc=0x974b8
Steps to reproduce
Run Tailscale version tailscale_1.18.2_mipsle on GL-MT1300 running OpenWRT
To fix the issue, the workaround is to reboot the router, delete old binaries, copy them again. And it starts working correctly.
Are there any recent changes that introduced the issue?
No response
OS
Other
OS version
OpenWrt 19.07.7
Tailscale version
1.18.2
Bug report
No response
What is the issue?
After 24 hours of usage, the binary of the architecture mipsle fails like this:
Steps to reproduce
Run Tailscale version tailscale_1.18.2_mipsle on GL-MT1300 running OpenWRT
To fix the issue, the workaround is to reboot the router, delete old binaries, copy them again. And it starts working correctly.
Are there any recent changes that introduced the issue?
No response
OS
Other
OS version
OpenWrt 19.07.7
Tailscale version
1.18.2
Bug report
No response