A drive image program is running in the background. I pointed xplorer2 to its destination folder, and it took a long time with no action. Task Mangler shows 92MB memory used by it!
Windows 2000; 512MB memory, 1.7GH processor
xplorer2 hogs memory
Moderators: fgagnon, nikos, Site Mods
-
caughran
- New Member
- Posts: 6
- Joined: 2004 Aug 10, 22:42
Damn, happened again!
When I restarted xplorer2, it started up in the folder the imaging software is using. I hit backspace, and it is valiantly struggling to leave that folder, using 99069KB of memory, and has used 17 seconds of cpu. Something is stuck.
Jim Caughran
-
fgagnon
- Site Admin
- Posts: 3737
- Joined: 2003 Sep 08, 19:56
- Location: Springfield
x2 by default tries to keep up with changes in folders it views.
So if you use it to watch a disk imager's real time progress, I am not surprised by your report.
You might try turning OFF autorefresh [Ctrl+Alt+R] to see if that helps.
Another issue is that x2 uses lots of memory viewing very large folders (tens of thousands of files); but that may not be the issue here, even though the large memory usage you report is symptomatic of it.
So if you use it to watch a disk imager's real time progress, I am not surprised by your report.
You might try turning OFF autorefresh [Ctrl+Alt+R] to see if that helps.
Another issue is that x2 uses lots of memory viewing very large folders (tens of thousands of files); but that may not be the issue here, even though the large memory usage you report is symptomatic of it.
-
caughran
- New Member
- Posts: 6
- Joined: 2004 Aug 10, 22:42
Memory use
Okay, but 90+MB still seems excessive to chase one file. Perhaps, if things are changing rapidly, it should limit its updates. I'm not sure why an update should require new memory.
Jim Caughran
-
nikos
- Site Admin
- Posts: 16295
- Joined: 2002 Feb 07, 15:57
- Location: UK