Hi,
I tried to follow your advice, but that doesn't work as expected:
mempool.bin changes its size and is pretty small when I restart, but grows afterwards, having a size of a bit more than
1 MB now, when it's in the buggy state of slowness again:
ls -l mempool.bin
-rw-r--r-- 1 christoph christoph 1249793 Jan 10 15:00 mempool.bin
Because it seems to be rebuilt anyway here, there's no point to trigger that via the UI, I think.
About the logs:
ls -l *log*
-rw-r--r-- 1 christoph christoph 514486 Jan 10 06:39 armorycpplog.txt
-rw-r--r-- 1 christoph christoph 1408612 Jan 10 14:59 armorylog.txt
-rw-r--r-- 1 christoph christoph 1078697 Nov 17 00:02 ArmoryQt.py.log.txt
As you can see, the last one hasn't changed since november, is that due to a change of the filename between versions, or are there configuration options for different types of logs, and which one do you need in this case?
I cannot do anything productive in the GUI as soon as the buggy behaviour is triggered, because there is no reaction to mouse clicks and keypresses for minutes, so exporting the log for you won't work, I need to copy the right file, or the relevant section from it.
I tried to rule out that other stuff interferes by elevating the priority of the python processes, but that doesn't help. Armory consumes about 100% of the CPU cycles on the core it is running on, but still has those timeouts.
Christoph