crash when starting #131
Labels
No Label
1app
2 apps
accessibility
android
before-beta
bug
duplicate
enhancement
first-contact
fixed
help wanted
infrastructure
invalid
low-priority
must-fix
needs testing
nice-to-have
question
tor
user-feedback
wontfix
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/ui#131
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
manually restarting non-bundled tor made the problem go away but it was replicable before doing so.
2019/03/05 12:54:24 connections/engine.go [INFO] Running cwtch peer on xxx.onion:9878
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x667c4a]
goroutine 34 [running]:
github.com/cretz/bine/tor.(*OnionService).Accept(0xc4200c6230, 0xc420098140, 0xc4200da100, 0xc42005bd78, 0x51d268)
/home/erinn/go/src/github.com/cretz/bine/tor/listen.go:301 +0x2a
git.openprivacy.ca/openprivacy/libricochet-go/connectivity.(*onionListenService).Accept(0xc4202fc0a0, 0x18, 0xc42005be78, 0x1, 0x1)
/home/erinn/go/src/git.openprivacy.ca/openprivacy/libricochet-go/connectivity/torProvider.go:56 +0x2e
git.openprivacy.ca/openprivacy/libricochet-go/application.(*RicochetApplication).Run(0xc4200e4120, 0x883b20, 0xc4202fc0a0)
/home/erinn/go/src/git.openprivacy.ca/openprivacy/libricochet-go/application/application.go:150 +0xaa
cwtch.im/cwtch/protocol/connections.(*Engine).listenFn(0xc4200a8500)
/home/erinn/go/src/cwtch.im/cwtch/protocol/connections/engine.go:152 +0x69c
created by cwtch.im/cwtch/protocol/connections.(*Engine).eventHandler
/home/erinn/go/src/cwtch.im/cwtch/protocol/connections/engine.go:104 +0xf89
Linking #128 as I expect they are related.
We keep seeing crashes caused by Bine and/or libricochet - we should double check the tor provider code to make sure we are correctly handling issues with contacting tor.
Haven't seen any crashing on startup for a while in all kinds of conditions, and based on Dan's experiments and the latest window code, I'm going to close this.