Hello,
I'm using supercopier for few years and now, when deprecated, ultracopier.
Since few few weeks my computer crashes some times.
Windows 7 Enterprise x64 with all updates, 8GB of ram.
Since I know where the problem comes from I upgrated to ultracopier 1.4.1.0 and doubled the ram to 16 GB, but still the same:
while transfering files over network (transfer queue is about 200 GB to 1TB consisting of files between 1KB and 25GB) after a while (sometimes after 1minute, sometimes after half an hour) ultracopier catches more and more memory until all memory is full.
I tried stopping the transfer and close ultracopier but the ram stays still full and the „FreeMem=Space(512000000)“ vbs-script won't work.
Yesterday I tried to restrict ultracopier via the tool "Process Lasso" by auto-free ram when getting over 2GB and it worked, but it seems that at some point ultracopier eats the ram faster then the tool can free or another reason that the process lasso tool failed (I was sleeping while the system hangs, didn't see this point exactly).
Some more infos about the network:
Host adapter: onboard Realtek 1GB ethernet on ASRock AM1H-ITX
target adapter: onboard Realtek 1GB ethernet on ASRock FM2A68M
network Switch: TP-Link AV1300 Powerlan (TL-PA8030P) - connection direct via gbswitch, not over powerline. I'm using powerline just for internet / connection to the router
So please can you help getting this great tool working again?
regards - Stefan
Ultracopier uses all ram memory on network transfer -> system chrashes
-
- Posts: 4
- Joined: Wed Aug 22, 2018 5:56 am
- alpha_one_x86
- Site Admin
- Posts: 1270
- Joined: Sun Oct 26, 2008 9:09 am
- Contact:
Re: Ultracopier uses all ram memory on network transfer -> system chrashes
Hi,
I can't reproduce this here. Into the option, can you reduce the buffer size?
Cheers,
I can't reproduce this here. Into the option, can you reduce the buffer size?
Cheers,
-
- Posts: 4
- Joined: Wed Aug 22, 2018 5:56 am
Re: Ultracopier uses all ram memory on network transfer -> system chrashes
thanks for your reply.
Which settings do you recommend?
I'm using these which are the same as on my old Windows XP notebook (but without ethernet connection and therefore other general usage)
Which settings do you recommend?
I'm using these which are the same as on my old Windows XP notebook (but without ethernet connection and therefore other general usage)
- alpha_one_x86
- Site Admin
- Posts: 1270
- Joined: Sun Oct 26, 2008 9:09 am
- Contact:
Re: Ultracopier uses all ram memory on network transfer -> system chrashes
Try reduce sequential buffer to 1024KB.
-
- Posts: 4
- Joined: Wed Aug 22, 2018 5:56 am
Re: Ultracopier uses all ram memory on network transfer -> system chrashes
Done but no effect
After a few minutes of transfer the ram usage is 12GB and I had to pause transfer curious: task manager it is just showing 24MB of usage for ultracopier this hapens when I stop transfer, ram usage falls to normal ~2GB
After a few minutes of transfer the ram usage is 12GB and I had to pause transfer curious: task manager it is just showing 24MB of usage for ultracopier this hapens when I stop transfer, ram usage falls to normal ~2GB
- alpha_one_x86
- Site Admin
- Posts: 1270
- Joined: Sun Oct 26, 2008 9:09 am
- Contact:
Re: Ultracopier uses all ram memory on network transfer -> system chrashes
Then I think the problem is not into Ultracopier.
The down of memory usage is due to cache flush produced by disk usage.
The down of memory usage is due to cache flush produced by disk usage.
-
- Posts: 4
- Joined: Wed Aug 22, 2018 5:56 am
Re: Ultracopier uses all ram memory on network transfer -> system chrashes
OK, and what does this mean?
I always have one transfer direction: from the Windows 7 machine with ultracopier over the network to the other machine
I always have one transfer direction: from the Windows 7 machine with ultracopier over the network to the other machine
- alpha_one_x86
- Site Admin
- Posts: 1270
- Joined: Sun Oct 26, 2008 9:09 am
- Contact:
Re: Ultracopier uses all ram memory on network transfer -> system chrashes
If I can't reproduce the problem, I can't fix it.
Try isolate the bug case, change the destination to local hard drive, always have problem on same file, ...?
Try isolate the bug case, change the destination to local hard drive, always have problem on same file, ...?