Topic: Electrum weird freezing on click (Read 187 times)

I wish I had seen this post before I tried everything else, but no, I don't remember!


Tor or opennet, both where experiencing issues.


That log that ends with "receiving history" also made me think the same.
I don't have thousands but I have +500, I don't know if the number of outputs and inputs matters but there is a ton of them, not simple tx, and this was probably, like 99.9% why it crashed. I played with an old virtual machine with an old electrum wallet I had, same version and it worked flawlessly but I had under 10tx per adress.
There is an advice about not reusing addresses that I should have taken seriously but it's so hard when running a business to keep changing your little cold storage.

Despite me being really later, thanks for the the comprehensive answer, 6 years and this forum is still better at getting replies that others like stack or reddit.


Noted!

Your Electrum is connected to an Electrum server which provides address history transactions and notifications of new transactions of all addresses in your wallet. If your addresses have a large transaction history or if you have used a lot of addresses in your wallet then there's quite some communication needed to get an update of your current wallet balance.

If you happen to be connected to a slow or throttling Electrum server and that server doesn't like the requests of your Electrum very much or can't process them in a timely manner, then you experience delays and possibly also the freezes you have. Throttling may occur when the connected Electrum server penalizes a lot of requests from your side.

When the freezes happen, do you see a green or blue (proxied) light in the right bottom corner or two arrow forming a circle?

When your Electrum has a blue light then you go through a proxy, possibly through Tor if that's configured. Tor can sometimes be quite slow which might then explain your freezes.

Problems can (but most not) show up when your addresses have a transaction history that goes into the thousands. If that's not the case for your wallet then something else is fishy. But it's hard to debug without logs or details that you might not want to disclose in public.

I'd first try other Electrum Servers and see if some simply perform better. Click on the green or blue light, the network dialog opens. When you right click a server you have the option to connect to this specific server.

I can't recommend one as I use my own fast Electrum server for performance and privacy reasons.

Bumping this as it seems it was just a one time solution, I switched to a new version and also stooped reusing addresses, so basically a fresh start as the issue were not fixed no matter what:

Guess this was the culprit:


all logs when it crashed stop at the history address I was currently using


+1
Noticed the same right now, but I think its 10 old and the current one, I watched it deleting the last one every time I opened it but there are always 11 files in the history.

Back to the topic, no advice to give to the ones that might encounter the issue, just an update of what didn't fix it! Just update and that's it!

Only ~10 log files are kept. If there are more, the oldest ones are deleted automatically.

I cleaned the app data folder, restored the wallet, moved a few sats between addresses, seems like the issue is gone.

BitMaxz
It's a Thinkpad i3 6th gen with 8Gb ram and a SSD, it's my own bought it new, I have no AV.
Transactions, might be, there are over 500 for sure.

nc50lc
I enabled the logs, wish I'd knew they need to be enabled before, but I will keep it like this in case this happens again and it was just a temporary fix, a few extra files don't matter I guess and I will delete them once in a while.

Thanks everyone!

Check if you can discover the cause,
However, I'd not recommend to submit it as issue to GitHub since it's for an old version.

Enable debugging in "Tools->Preferences->Write logs to file", restart Electrum.
After reopening, reproduce the issue and then find the logs in: /logs folder.
The default Electrum data directory in Windows10 is in %appdata%/Electrum (paste it on your "Windows Explorer" or "run" window)
Open the log file with a text editor and check if there's any error related to the issue.

Don't forget to disable logging later or Electrum will produce a log file in every session.

Your wallet might have lots of transactions.
Would you mind sharing the specs of your laptop?

You maybe need to manually increase your virtual memory to fix this issue can you try it first? I suggest 4,096mb virtual memory.

Also, try to disable AV or add your Electrum as a trusted app and exclude it from scanning then update here.

OmegaStarScream, I will try that for starters.
Cricktor, no idea about the servers, I never thought of that as a possible issue, it's on auto, I guess probably default settings and random server each time?

The back-ups are safe and not on the same machine, so I'll just try the two above and if keeps acting even after this I will probably just switch to 4.4.

Before you do that, to which Electrum server is your Electrum wallet connected? Does the behavior of your wallet change if you change to another Electrum server?

If your Win10 box isn't an air-gapped setup, you still might consider to update your Electrum as I don't see a benefit to stay on that old version of yours. Before you update your Electrum, make sure to have backups of your wallet files in case you want to revert back to your old Electrum version. Newer Electrum versions update the wallet files to their version and to my knowledge and personal experience to can't open a newer wallet file version with an older Electrum software version.

Make sure that you have your wallet's seed first, and then try to delete the folder:


Run Electrum again -> Restore your wallet (with the seed) and see if the problem persists. If it does, then I guess you should just go ahead and update. It's always recommended to use the latest version anyway.

Every single one, have done 4 transactions in the past week, every time it freezes, if I just close the window, and then pick the tx from the history to grab the hash there are no issues.
It's annoying and the fact that I haven't found the bug on github makes me a bit uneasy! So update??

I tried the 4.0.9 portable version, and I couldn't reproduce the problem you're having. Does this happen with any transaction you make or just with a specific one?

Wallet version 4.0.9, OS Windows 10 Pro (yes, I know), clean install, laptop is used only for coins.

Never had a problem with it, never triggered any error until because of the fluctuating fees I tried to copy the hash after making a transaction to see where it sits in the mempool, did it a few more tests after the first issue, no matter how long I wait if I click anywhere in the transaction window other than close  the whole wallet freezes and becomes unresponsive.
I assume there is no other fix than update to  4.4 ?!?