Skip to content

fatal error: concurrent map writes in 1.08 & 1.09 after some minutes #171

@sqw534

Description

@sqw534

When I run wireproxy 1.08 or 1.09 in Windows I receive a fatal error after some minutes.
I can restart the exe but this bevaviour appears again.
In 1.07 this does not happen.

Command beig issued:

wireproxy.exe -c C:...\wg.conf

DEBUG:` 2025/04/12 12:41:54 peer(...) - Routine: sequential sender - started
DEBUG: 2025/04/12 12:41:54 peer(...) - Sending keepalive packet
DEBUG: 2025/04/12 12:41:54 peer(...) - Sending handshake initiation
DEBUG: 2025/04/12 12:41:54 peer(...) - Routine: sequential receiver - started
DEBUG: 2025/04/12 12:41:54 Interface state was Down, requested Up, now Up
DEBUG: 2025/04/12 12:41:54 peer(...) - Received handshake response
fatal error: concurrent map writes

goroutine 239 [running]:
github.com/pufferffish/wireproxy.VirtualTun.pingIPs.func1()
/home/runner/work/wireproxy/wireproxy/WireProxy/routine.go:478 +0x6a5
created by github.com/pufferffish/wireproxy.VirtualTun.pingIPs in goroutine 67
/home/runner/work/wireproxy/wireproxy/WireProxy/routine.go:438 +0x7d6

goroutine 1 [chan receive, 1 minutes]:
main.main()
/home/runner/work/wireproxy/wireproxy/WireProxy/cmd/wireproxy/main.go:247 +0xb6d

goroutine 6 [syscall, 1 minutes]:
os/signal.signal_recv()
/opt/hostedtoolcache/go/1.21.9/x64/src/runtime/sigqueue.go:152 +0x29
os/signal.loop()
/opt/hostedtoolcache/go/1.21.9/x64/src/os/signal/signal_unix.go:23 +0x13
created by os/signal.Notify.func1.1 in goroutine 1
/opt/hostedtoolcache/go/1.21.9/x64/src/os/signal/signal.go:151 +0x1f

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions