Was running fine. Closed it. Connected treZor to check something. While treZor was running (google chrome) I started WasabiWallet. Wasabi starts up and after about 5 seconds it hangs and requires a force-kill.
Even after I shut Trezor and all chrome instances the wasabi wallet will hang again and requires a force kill.
Reboot did not solve it.
Uninstalling and re-installing wasabi did not solve it (still hangs).
Recovering the wallet did not help (freeze again).
Deleting ~/.walletwasabi did not help either. Hangs immediately (before trying to recover the wallet)
Uninstalling, deleting ~/.walletwasabi and re-installing does not solve it either. Freezes after 5 seconds and becomes unresponsive (same error).
macOS Mojave 10.14.6
Wasabi Client Version: 1.1.7
Compatible Coordinator Version: 3
@SkyperTHC Could you check the logs pls? Or did you already deleted them too? If you have deleted your config there is a bug which will prevent you to use Wasabi:
https://github.com/zkSNACKs/WalletWasabi/pull/2263
I could not reproduce the issue. My trezor found every time and Wasabi is not hanging even after several minutes.
the issue went away after i updated to 1.1.18.
Want me to try and reproduce it again on 1.1.17 and send you the debug log?
On Fri, Sep 13, 2019 at 5:16 PM Dávid Molnár notifications@github.com
wrote:
I could not reproduce the issue. My trezor found every time and Wasabi is
not hanging even after several minutes.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zkSNACKs/WalletWasabi/issues/2261?email_source=notifications&email_token=ABNJ2QXJOWSKGQPJJEU2AGLQJO4HHA5CNFSM4IWPJTDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6VQCFI#issuecomment-531300629,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNJ2QTGAEMOTXHWHFDQTX3QJO4HHANCNFSM4IWPJTDA
.
I think it was an accidental crash because from 1.1.7 we only changed some UI stuff and we did not touch the HWI code. After you deleted Wasabi data folder you faced this problem: https://github.com/zkSNACKs/WalletWasabi/pull/2263
So it should be fine. However, if it happens again during the usage of Trezor pls let me know and we will start debugging.
Oh I closed accidentally if you OK with that pls close the issue.
@SkyperTHC Could you check the logs pls? Or did you already deleted them too? If you have deleted your config there is a bug which will prevent you to use Wasabi:
2263
Updated to 1.1.18. Recovered wallet with recovery passphrase.
Was running fine for hours and now it's freezing every 5 seconds again.
You mean ~/.walletwasabi/client/Logs.txt? nothing suspicious in there.
When starting and not doing anything it hangs after 5 seconds.
Last entries are:
[..]
Start connecting to nodes...
Start synchronizing filters...
When clicking on the GUI to load the wallet then the last entries are a bit different...
[...]
Start cleaning out mempool...
334 transactions were cleaned from mempool.
My guess is that it is UI related, but I have to get a starting point to debug this.
I updated to 1.1.8 and bug still happened. I updated treZor firmware and bug did not happen again (not sure if there is a correlation/causation or coincident).
Now running for the last 24h on 1.1.8 with treZor (latest firmware) connected and stable.
BTW there is a 1.1.9 release.
https://github.com/zkSNACKs/WalletWasabi/releases/tag/v1.1.9
running for 48h now with treZor connected without freeze....happy to close this case and Ill report back if it happens again.
Just restarted wallet and hangs again after 5 seconds. Happens on every restart now. Seems to be similar to bug #2279. Regardless if trezor is connected or not. Version 1.1.8. Noticed that it say "Connecting..." at the left bottom (rather than "Ready".).
Send me an email and I can send you the sample of the process (stack dump etc). skyper at thc dot org.
BTW there is a 1.1.9 release.
Can you try the last version? and see if you still have this problem.
Sent email.
Just an update: This problem did not happen again with 1.1.9 so far (4 days running stable. Multiple restarts. Multiple Trezor connects and disconnects).
Nice to hear that. Feel free to close this issue.
I will close this, it looks like the problem solved.
Most helpful comment
Just an update: This problem did not happen again with 1.1.9 so far (4 days running stable. Multiple restarts. Multiple Trezor connects and disconnects).