uTorrent Crash - Large cache

[halabb]

(Windows Server STD 2003 x64, Tyan 5197, E6420, 4GB Patriot nonECC)

I want to use 2GB+ for uTorrent.

I initially set it for 2768MB. I saw "Disk overload 100%" at the bottom of the status bar and the transfer rates were beyond slow.

I set it to 2GB. It ran for a few hours using the full 2GB cache until it crashed.

Before the RAM upgrade on the server, I had the cache @ 768MB. I set it to 1GB last night and didn't have a problem.

I just set it to 1536MB and I'll keep increasing till I hit my 2816MB max.

Any clues on why it might be crashing at 2GB+?

[jewelisheaven]

I'm sorry but you are not the first to have reported issues with disk cache set > 1023 MiB.

A form search with disk cache will provide you with similar reportings.

[halabb]

Just came back home to see it crashed when set at 1536MB.

****************edit

Forgot I had the pagefile set to 1536MB!

Set it to 4096 expandable to 8192 and uTorrent has been running for over 6 hours with a cache of 1526MB! Hopefully that's my fix. I'll find out when I increase it to 2GB+.

Lemme know if you care to know the results.

[ajones81]

Do let us know what was the largest you got the cache to be with a stable uTorrent.

[Firon]

The cache can never go beyond 2GB. It's a 32-bit app. If the memory usage goes beyond 2, it will crash.

[halabb]

...As for 32-bit appz being unable to address 2+GB RAM...

I consider that the same as 32-bit OSes addressing a max of 4GB.

I thought it was impossible for a 32-bit OS to address more than 4GB.

I was wrong. And nothing is impossible. Lookup: PAE (Physical Address Extension)

As for uTorrent, I am on 1400MB cache so far without a problem. I have incremented 100MB from 1GB.

[Firon]

PAE allows certain OSes (only certain server editions of Windows can, ignoring linux) to go beyond 4GB, but userland processes are still limited, unless they use something like AWE.

[halabb]

Well, it just crashed when I upped the cache to 1475MB. So somewhere between 1450MB and 1475MB there is a max. I'm just keeping it at 1450MB.

I demand a 64bit uTorrent application. Screw the unicode mumbojumbo. If you don't have a 64-bit CPU *(@*&$_).

Make like Microsoft and phase out the old technology.

[jewelisheaven]

Hey I didn't mention this before but I presume you're using the latest stable? 1.7.5 is good, but there have been some changes in the 1.8 line related to this usage highlighted here. Do you think you could try running the same setup (although limited implementation of the resume, since it is quite a drag to try and multi-task identical settings for multiple instances) with a limited "test" run on 1.8 to see how it fares?

I must say though... seeing a natively compiled x64 µT would be quite spiffy. I'd imagine that wouldn't possibly happen until at least 1.9, since 9x support is still maintained and actively requested feedback upon (just read rafi's posts ) I am amazed at how 1.8 makes things more transparent and easier... I thought 1.7 was as good as it gets, and I'm happy the development team continues to prove that thought incorrect.

[halabb]

Ya... I'm using 1.8 (7041).

I have yet to test uTorrent with a similar cache size on another server.

I just increased the PF to 8GB (double my RAM). Maybe thats my miracle cure. [ha]

Does anyone else have a problem with using 1475MB+????

-------------------------------------------------------------edit

uTorrent's virtual space creeps up to 2,023,000K and sometime after that crashes.

uTorrent is set for 1400MB. Not sure why it keeps increasing. Finding out when it stops crashing...