EOSCommunity.org Forums

Anchor on Ubuntu 20.04.2 LTS

Greymass Anchor Wallet
#1

Just installed Anchor “linux-anchor-wallet-1.2.1-amd64.deb” on Ubuntu 20.04.2 LTS. When I run it, the main window doesn’t show up on the desktop. Only the system tray icon on the top right is visible. It is also not visible under Ubuntu Softwares Manager but is visible when viewed via “Show Applications”. Also noticed that under System Monitor processes, there are a few instances of Anchor and the memory for one of them keeps rising even when idle. I had to end the process as it kept rising above 2 GiB! The Appimage version also displayed the same behavior.

Prviously, linux-anchor-wallet-1.1.12-amd64.deb installed and ran perfectly in Ubuntu 18.04 LTS.

Has anybody else reported this issue?

#2

First time I’ve heard of it. I just used the deb to install 1.2.1 the other day on an Ubuntu 20.04 machine for testing and I didn’t see this :thinking:

I’d be curious to know if there are any errors in your local log. It can be found here:

~/.config/Anchor\ Wallet/log.log

By design there shouldn’t be any sensitive information in there, but might want to double check before sharing anything.

#3

More clues. Fresh install works great until I click enable ledger support. Then it gets stuck. This is when the memory starts piling up.

Log file looks ok:

[2021-04-11 21:02:51.352] [info] wallet ui: creating
[2021-04-11 21:02:51.377] [info] protocol handler: creating ui
[2021-04-11 21:02:51.377] [info] initial request false
[2021-04-11 21:02:52.064] [info] [ ‘networkStatusChanged’, ‘online’ ]
[2021-04-11 21:02:52.095] [info] protocol handler: loaded ui
[2021-04-11 21:02:53.374] [info] manager: loaded
[2021-04-11 21:03:53.601] [info] enableSigningRequests
[2021-04-11 21:08:13.146] [info] anchor: initializing
[2021-04-11 21:08:13.204] [info] anchor: ready
[2021-04-11 21:08:13.204] [info] enableSigningRequests
[2021-04-11 21:08:13.231] [info] signing requests
[2021-04-11 21:08:13.231] [info] tray menu: creating
[2021-04-11 21:08:13.242] [info] creating tray menu
[2021-04-11 21:08:13.243] [info] /opt/Anchor Wallet/resources/app.asar/renderer/assets/icons/png/32x32@2x.png

#4

Never mind Aaron. Issue is fixed at my end. After upgrading to Ubuntu 20.04. I needed to add the udev rules in order for the Ledger to connect as described here

However, you might want to check why Anchor didn’t complain about a connection issue and there was a memory leak. After the connection issue was fixed with the udev rule, the memory usage is sitting around 135-140 MiB.
Thanks.

#5

Hi Aaron,
Found another minor bug in the Linux version of Anchor in Ubuntu. The functions of “Close Window” and “Exit Anchor” in the File menu are switched. One performs the other.

1 Like
#6

I think our reconnection logic to the Ledger might be the cause here. It might aggressively be trying to reconnect when it was blocked, and keeping log entries from all those attempts in the application state.

I’d have to try to reproduce and see if I see the same leakage occurring.

#7

Good catch… that’s probably been that way for ages. Fixed in:

That’ll be included in the next release.

#8

:+1: Thank you. On the ledger re-connection logic, maybe Anchor can attempt re-connection a certain number of times and if unsuccessful, quit trying and spit out an error message saying something like “Anchor cannot connect to your Ledger Device. Please make sure that you are able to connect to your Ledger device with another app. If the connection issue persist, please visit Ledger support website.” The reason I say this is because I figured out the connection issue only after trying to connect to the ledger with the Ledger Manager app and failing. It wasn’t Anchor’s fault, it was just that I had not added the udev rules to support Ledger connection after my fresh Ubuntu install.

1 Like