[BUG] TotalCmd crashes while moving files

[ghisler(Author)]

I cannot repeat here what you report, sorry. I'm using two tools (memory sleuth and Numega BoundChecker) to make sure that TC has absolutely no meory leaks!

However, some device drivers seem to accept data for copying and report that it's copied, while they just put it in their internal cache (which then overflows). To avoid this, try the following settings in your wincmd.ini:

Under [Configuration], please add
CopyBlockSize=1024
CopyHugeBlockSize=10240
CopyBlockSizeOther=128
CopyHugeBlockSizeOther=1024

This will bypass the Windows disk cache and write directly to the disk. Please be careful because some bad device drivers don't seem to work with this, or work very slowly.

[Innuendo]

Thanks for the suggestion, Christian, but those settings are already present in wincmd.ini. That was one of the first tweaks I did to the ini file.

Any other ideas?

[pdavit]

Let’s follow some more troubleshooting Qs and As to help Christian:

1. Do you get the same behaviour if you copy the files instead of moving them? (I presume this will cause less memory consumption)

2. It that folder you are talking about a network folder by any chance?

3. I guess we can withdraw the chance of defective files because you said that Explorer does the job without any problems and TC works fine if you split that colossal task into smaller segments. Are you using a beta version of TC and if not are you using the latest one?

4. You said your OS is WinXP. Are you running in FAT32 or NTFS?

5. Is there enough free space on your hard drive to handle this colossal moving task? (and that is on the source location not the destination)

6. What are your swap file configurations?


Remark: Why on earth do you keep 17,845 files on a single folder? You don’t like the idea of directories?

[Innuendo]

I'm all for troubleshooting. I just want to get this fixed.

1. Yes, same problem if I just copy instead of move.

2. No, no network folders. All local drives.

3. Using the latest non-beta...5.50 Silent Update 1

4. Yes...WinXP SP1. NTFS on both the source and destination drives.

5. This last go around the source drive had 160 GB free...destination 70 GB free...should be enough, yes?

6. Swap file is set to 512-1024 MB.

I love the idea of directories, but this was sort of a catch-all directory for a bunch of downloaded/lumped-together files and I was moving a bunch of stuff to one hard drive before I undertook the task of sorting all those files into smaller, more manageable directories.


Thanks for the assist, pdavit...judging from Christian's replies, I don't think it's a TotalCmd problem, but a Windows one & hopefully with help, he can work out a work-around for the problem.

[Renard_Roux]

2Innuendo
Let me give a wild guess on your prob. Maybe some part of your bunch of files are archives. In this case if you use zip magic you should turn it off:

wincmd ini:
[Configuration]
...
ZipMagic=1

[Hacker]

Innuendo,
O&O CleverCache

Could this be your problem?

HTH
Roman

[Innuendo]

Renard_Roux, no...I don't use ZipMagic & all the files are JPGs. Good suggestion, though.

Hacker, I installed O&O CleverCache *after* I experienced the problem hoping that CleverCache would help with the problem. It didn't.

I guess this problem will go away once I sorted all the files out of the directory, but it just annoys me that this is a problem currently without a real solution.

[aguirRe]

I made a quick test using TC5.5 and a directory with over 14000 files totalling over 2GB and I also couldn't experience any problems either moving or copying. I especially watched for accumulating memory consumption and there was none, just about 5-7 MB which is normal for TC.

System is a P4 1.7 GHz running WinXP (no SP), 512 MB RAM and a 80 GB HD with NTFS.

[Innuendo]

aguirRe,

Thanks for your test...only difference between what you posted as being in your system is I have a P3-1GHz...XP SP1...and 384 MB RAM rather than 512.

Sigh...it's probably as Christian said...a rogue driver for some piece of hardware that I have that you don't.

[Innuendo]

Ack...I think I found my problem. I have a Promise Ultra100 TX2 controlling my hard drives.

I upgraded my driver and that problem went away. Unfortunately, now I'm having problems in other areas.

Sigh...computers are so frustrating sometimes.

Sorry I suspected your program, Christian!

[Floppo]

I have the same problem, but in my experience it only occurs when the folders involved in the move or copy have descript.ion files (and the File Comments support is enabled).

If I disable the file comments support I have no problems moving the same folders.

Right now I'm looking at the taskmanager with TOTALCMD.EXE using 214.772K memory, growing apx 500K/sec.

[ghisler(Author)]

I'm not aware of any memory leak in the copy comments function, but I will make some tests to confirm this.

[Innuendo]

I have the same problem, but in my experience it only occurs when the folders involved in the move or copy have descript.ion files (and the File Comments support is enabled).

Holy crap, Floppo!!! When I was having the problems I was indeed trying to copy a directory that had a descript.ion file in it!

Great detective work!!!

And yeah, I experience TC ballooning in memory use all the time. I have learned to just live with it.

[JackFoo]

Erm, sorry to bump an old thread, but I've experienced the same thing with TC, memory leaked to around 220Megs with no way to release it. (I had enough memory for it not to crash)

I never expereince it with w2k but I'm now on winXP+sp1+(all updates) and copying ~8gb of data between disks while one dir contained a couple of thousands of small files (~1k each) created this behaviour. Later looking at the Cache (using sysinternals cacheset) I've noticed the same rise in current cache size.

I'm using Christian's suggestion for CopyBlockSize etc.; I had IE, and mIRC open at the same time no firewall/av/caching program. Seems like a winXP + TC copy problem involving lots of files...

Cheers.

[Hacker]

Any descript.ions inside?

TIA
Roman