Splash Screen Occasionally Takes Far Longer to Clear #633
Labels
No Label
android
arch
backlog
blocked-on-external
bug
bugbash
component/bindings
component/bine
component/connectivity
component/cwtch
component/tapir
component/ui
cwtch-1.14
cwtch-1.15
cwtch-beta-1.1
cwtch-beta-1.10
cwtch-beta-1.11
cwtch-beta-1.12
cwtch-beta-1.13
cwtch-beta-1.2
cwtch-beta-1.3
cwtch-beta-1.4
cwtch-beta-1.5
cwtch-beta-1.5.x
cwtch-beta-1.6
cwtch-beta-1.7
cwtch-beta-1.8
cwtch-beta-1.9
design
duplicate
enhancement
flutter
funding-needed
help wanted
hybrid-groups
in-nightly
in-progress
invalid
ios
linux
mac
need-replication-or-investigation
ops
packaging
post-stable
question
questionable
requires-more-effort-than-we-can-spare
rust
scheduled
stable-blocker
tails
testing-needed
tests
tor
waiting-on-fix-confirmation
waiting-on-new-flutter-feature
whonix
windows
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch-ui#633
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?
Based on my testing, every so often cwtch will launch and be stuck on the splash screen for far longer than normal - up to a minute.
My guess is there is some subtle asynchrony issue which every so often forces the splash screen to wait a long time for the clear message - perhaps an event bus flood?
This has little impact except annoyance and the occasional failed pipeline test (because splash screen dismissal times out at 10 seconds)
My experience is that cwtch does take a long time to get past the splash screen, but took 1m22s to display the purple screen at all - the splash screen gives way to the program itself after a total of 2m22s. Testing again gives values of 1m9s for a blank screen, and the graphic appears until a total of 2m12s have passed.
Running cwtch from the terminal returns...
...and remains onscreen for 1m6s. After this, the following appears as the splash screen shows up.
After a total of 2m12s, the the terminal does not update, but the splash gives way to the program and this output remains. Pls let me know if any more info would be useful. :3 I'm using herbstluftwm as my wm.
Update on this based on yesterdays research:
This is caused by Cwtch being unable to connect to a Tor process. It can happen for a few reasons:
The solution to this is a change to autobindings to rework the setup so that the splash screen logic no longer depends on connecting to Tor. This used to be a big problem, but after recent changes to how protocol engines are created and initialized should be pretty easy to fix.
Any Tor errors will then only be surfaced on the Tor config page.
This should get in 1.12
Fixed by cwtch.im/autobindings#29