Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIGSEV: Segmentation violation #208

Open
ToddAlvord opened this issue Feb 1, 2023 · 0 comments
Open

SIGSEV: Segmentation violation #208

ToddAlvord opened this issue Feb 1, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@ToddAlvord
Copy link

ToddAlvord commented Feb 1, 2023

After loophole has been running for some time, I get the following error

7:52PM ERR Dialing into local proxy for HTTPS failed
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x109e0d7]

goroutine 2231 [running]:
io.copyBuffer({0x2a347058, 0xc0003cec90}, {0x0, 0x0}, {0x0, 0x0, 0x0})
	/opt/hostedtoolcache/go/1.18.0/x64/src/io/io.go:426 +0x197
io.Copy(...)
	/opt/hostedtoolcache/go/1.18.0/x64/src/io/io.go:385
github.com/loophole/cli/internal/app/loophole.handleClient.func1()
	/home/runner/work/cli/cli/internal/app/loophole/loophole.go:44 +0xa5
created by github.com/loophole/cli/internal/app/loophole.handleClient
	/home/runner/work/cli/cli/internal/app/loophole/loophole.go:43 +0x15d

image

To Reproduce
Steps to reproduce the behavior:

  1. Running loophole for >12 hours seems to do the trick

Expected behavior
I expect loophole to not crash, or to at least exit gracefully

Environment

  • OS: MacOS 13.1
  • Version: 1.0.0-beta.15 (5cef33)
@ToddAlvord ToddAlvord added the bug Something isn't working label Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant