File Explorer (Manager) Crashes Repeatedly
Posted: Thu Jun 23, 2016 6:58 am
OK, I know ...
this is an old problem,
but I have a very specific scenario,
and I am sick & tired of being brushed off
on various forums (not here !) with empty phrases like :
live with it, can't be fixed, not our fault - blame Windows,
give up Your favorite programs, etc.
I would like to compare notes with people who have similar issues,
and see how they (hopefully) fixed the issue,
or maybe we can figure out something together.
The "old theme" is this :
You are using Your default File Manager (for example Windows Explorer, XYplorer, Double Commander)
for normal "file work", which includes using the context menu (right-click),
and after 9 or 10 times the File Manager crashes (freezes, goes "funny", won't take Your commands. etc).
You then restart the File Manager, everything is fine for a little while, and then it happens again.
@ I have often found workarounds for bad shell extensions, especially by using links in "Send To".
Here is the specific scenario :
Starting with Windows 8, the "Send To" cannot have Sub-Folders inside it
to neatly sort out (sub-divide & classify) the various Send To links that I would like to use.
So, I resorted to the portable FileMenuTools for this.
My default File Manager is the portable XYplorer.
Developers of both these programs told me basically
"it's not our fault, blame Windows for this".
The XYplorer guys were polite, but had no further ideas,
the FileMenuTools developer stopped responding to my further communications
but made a very interesting observation in his last response :
watch in Task Manager how Explorer is "pumping up" (increasing) RAM
each time You use the context menu, and this non-releasing or RAM crashes it eventually.
This is the creative solution that I am trying to figure out :
I applied a RAM cleaner MiniMem, and I tuned up it's settings so that
it releases unused memory every 100 seconds from only 2 programs - XYplorer, and (Windows) Explorer.
Now the situation is much improved :
the crashes that used to occur every 5 minutes, now occur maybe every 45-60 minutes.
Am I onto something here ?
I wrote to the FileMenuTools developer about this,
I suggested that he builds something into FileMenuTools
that cleans up the elevated RAM after each use,
but I never heard back from him again.
Here is what I would like to avoid :
Yet another "give up on software" (like FileMenuTools & XYplorer here).
I have disabled every other shell extension that I can think of,
and yet the Explorer RAM keeps going up with each context menu use.
Appeal to You (who are reading this) :
Did You have similar experiences ?
What did You learn from them ?
Any suggestions ?
Any brave programers who want to look into this Explorer RAM issue ?
I thought RAM cleaners are ancient history, but maybe not ?
this is an old problem,
but I have a very specific scenario,
and I am sick & tired of being brushed off
on various forums (not here !) with empty phrases like :
live with it, can't be fixed, not our fault - blame Windows,
give up Your favorite programs, etc.
I would like to compare notes with people who have similar issues,
and see how they (hopefully) fixed the issue,
or maybe we can figure out something together.
The "old theme" is this :
You are using Your default File Manager (for example Windows Explorer, XYplorer, Double Commander)
for normal "file work", which includes using the context menu (right-click),
and after 9 or 10 times the File Manager crashes (freezes, goes "funny", won't take Your commands. etc).
You then restart the File Manager, everything is fine for a little while, and then it happens again.
@ I have often found workarounds for bad shell extensions, especially by using links in "Send To".
Here is the specific scenario :
Starting with Windows 8, the "Send To" cannot have Sub-Folders inside it
to neatly sort out (sub-divide & classify) the various Send To links that I would like to use.
So, I resorted to the portable FileMenuTools for this.
My default File Manager is the portable XYplorer.
Developers of both these programs told me basically
"it's not our fault, blame Windows for this".
The XYplorer guys were polite, but had no further ideas,
the FileMenuTools developer stopped responding to my further communications
but made a very interesting observation in his last response :
watch in Task Manager how Explorer is "pumping up" (increasing) RAM
each time You use the context menu, and this non-releasing or RAM crashes it eventually.
This is the creative solution that I am trying to figure out :
I applied a RAM cleaner MiniMem, and I tuned up it's settings so that
it releases unused memory every 100 seconds from only 2 programs - XYplorer, and (Windows) Explorer.
Now the situation is much improved :
the crashes that used to occur every 5 minutes, now occur maybe every 45-60 minutes.
Am I onto something here ?
I wrote to the FileMenuTools developer about this,
I suggested that he builds something into FileMenuTools
that cleans up the elevated RAM after each use,
but I never heard back from him again.
Here is what I would like to avoid :
Yet another "give up on software" (like FileMenuTools & XYplorer here).
I have disabled every other shell extension that I can think of,
and yet the Explorer RAM keeps going up with each context menu use.
Appeal to You (who are reading this) :
Did You have similar experiences ?
What did You learn from them ?
Any suggestions ?
Any brave programers who want to look into this Explorer RAM issue ?
I thought RAM cleaners are ancient history, but maybe not ?