XYplorer Beta Club

Well, my success is holding on day 5.

As I said above, I disabled my RAM cleaner 5 days ago.

Then I noticed that I also had "Trim Memory" enabled on Process Lasso,
I am not quite sure if I disabled this 5 or 4 days ago.

In this time, I only had 1 crash 4 days ago,
and I am not sure if at that time I had "Trim Memory" disabled or not,
from this perspective - probably not (yet).

Although I a not an expert, it SEEMS to me that
Process Lasso can not be made "crash-proof" if it is deprived
of the RAM that it needs.

It also SEEMS to me that "proofing" XY against bad shell extensions
is either impossible or very difficult - because XY inevitable
must rely on some aspects of Windows' File Explorer.

In conclusion, I wanted to change the title of this post from
"XYplorer crashes - can You make it more crash-proof ?"
to "XYplorer crashes - can You ... ? - SOLVED"
but I could not figure out how to do that.

Cheers !

Thanks for the report. Glad to hear it!

I changed the title of the first post to change the thread title.

So to make sure this is really the culprit: Enable your ram cleaner and the trim memory function in process lasso again and run this combination until you get another crash.
If you get one, disable process lasso. Run it again till the next crash. If you get one disable the ram cleaner again. Crash free after that?

Why?
Because we want to know which of the two programs exactly leads to these crashes...

OK, will do.

But it might take me a few days
to give You the answer.

On September 19th I resumed using both "Reduce memory" and "Process Lasso", I even increased the RAM cleaning of "Reduce memory" to every 30 seconds to make it "more aggressive".

Now it is September 22nd ... result : not a single crash.

I have not changed anything else on my system, parallel programs (running in background) are the same, no Windows updates either ... the only thing that is new is the XYplorer version. When I started this post, I was using version 26.30.0200, I did not upgrade for that "Rookie License" thing (because it is irrelevant to me - I am a "lifer"), I only upgraded to 26.40.0006 beta when admin here suggested it (updated error messaging, did not fix the problem), then shortly after that I updated to 26.40.0100 (which I am using now). I wonder if there is something in 26.40.0100 that fixed it, otherwise I am totally at a loss. But my problem is gone. Right now, I am quite busy with my personal life, so I would not have the time to go back to previous XYplorer versions to try to perhaps pinpoint things down any further, although the description above seems to do it (I think).

So, this is the feed-back that I can give, as promised.

Thanks !

Well, if adding error messages now fixes the bug, I won't shoot the messenger.