[BUG] TotalCmd crashes while moving files

[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

[JackFoo]

Any descript.ions inside?

Nope, don't use descriptions (they are disabled).

Cheers.

[Viking]

I have exactly the same problem (EOutOfMemory) when moving a large number of files.

I use WIN2K, have the same Ultra 100 TX2 EIDE card (but with the latest drivers) AND I use descript.ion....

Has the source of this bug been located now?

[Hacker]

That might be fixed with 6.0.

HTH
Roman

[jmccrary]

How does one monitor memory usage?

[j.x]

How does one monitor memory usage?

Try the Task Manager (Ctrl+Shift+Esc), then click the Processes tab.

[Backkom]

I'm using TC 6.55 public beta 2 and if I copy more then 60.000 directorys (without any files) I get the EOutOfMemory Error.

If the Error appears TC has a memory-usage from over 100MB.

I'm using Windows Server 2003 and coping the directorys over the network to an other Windows Server 2003.

P.S. If there are files inside of the directorys, it works with more than 60.000 dircetorys and the memory-usage is normal at 8MB.

Greetings
Backkom

[ghisler(Author)]

Thanks for your report, I will check what the problem could be. It's strange because no memory is allocated for copying the directories themselves...