FlashFXP loses UI functionality when time passes

This bug has been reproduced so many times on multiple PCs that I believe it is an actual bug.

Step to reproduce:

1. Start FlashFXP 5.4 b3970
2. Do some random things like connect and download.
3. Idle for couple days or weeks. (YES I know this step is gonna be very painful)
4. Come back and do some random things like connect and download.

Observed:

1. Queue panel no longer refreshes unless you manually scroll or click your mouse above that panel.
2. Log panel no longer refreshes unless like above.
3. Progress bar no longer refreshes.
4. Speed meter keeps zero bytes per second.

And:

1. No matter how you use a FlashFXP instance, idling or frequently using it to upload or download, it happens.
2. No matter how many instance windows you keep on your desktop, they all gonna become like this, sooner or later.
3. Multiple reproductions on my local PC, on my NAS (Server 2012R2 via RDP) and on my laptop.


This is gonna be a bug that's super hard to debug, but it is also annoying that I have to close all my windows and restart them every couple days.

Let me know if you need more information about this.

I suspect that maybe the memory allocated by FlashFXP is being moved from physical to virtual memory to make way for other processes that are actively being used, this is a common issue for any program under these conditions.

I have done long running tests and I have seen similar issues when low memory conditions are encountered while FlashFXP is running in the background, though the end result depends on the situation.

FlashFXP with a transfer queue running in the background behaves quite differently than simply idling in the background.

I doubt it's related to that memory issue. My NAS has 8G of RAM and constantly 2G is used, leaving 6G available.

Also I disabled pagefile so technically it has no chance to be swapped out.

Since your initial report I started testing this again on one of my machines and so far FlashFXP has a 100+ hour uptime without any issues.

I am not sure what to make of the problem that you encounter.

My computers usually maintain an uptime of at least 2 months before a restart, so I'd say give it a bit more time if possible.

Got ProcessExplorer to check the process start time:

Processes that don't work correctly were started at:
1/29
1/30
2/25

Processes that still function nicely were started at:
3/18
3/31

As of today, 4/11.

So, you'd expect 1 month plus on the uptime to cause issues.

Noticed this too.