Jump to content

Enormous UTP.LOG files (~80GB)


equazcion

Recommended Posts

uTorrent 2.2.1 build 23271 under Win7 x64

AMD Phenom II X4 / 4GB RAM / 320GB HD

I used WinDirStat to pinpoint the source of my hard drive space issue -- my free space keeps going down inexplicably -- and found 4 utp.log files. I'm actually not completely sure this is a uTorrent issue, because the files are located under Mozilla and Windows paths (see below), however when I googled around, the only information I found pointed to uTorrent.

File locations:

Program Files (x86)/Mozilla Firefox/utp.log (82.1GB)

Program Files (x86)/Mozilla Thunderbird/utp.log (6.2GB)

Windows/System32/utp.log (65.2GB)

Windows/SysWOW64/utp.log (65.2GB)

Low space warning bubbles show up while uTorrent is running. The sites I've found say these files log UTP/UDP connections...? There really wasn't very much information anywhere on these files though.

The files were too large to view normally, but I was able to examine them using Winhex. Here's a couple lines:

[10976011] 0x0bf2d3e0: CheckTimeouts timeout:9 max_window=1415 cur_window=0 quota=7090 state=CONNECTED_FULL cur_window_packets=1

[10976011] 0x0bf2d1b8: CheckTimeouts timeout:1252 max_window=1415 cur_window=0 quota=7090 state=CONNECTED_FULL cur_window_packets=1

Most of the file seems to look like this, but I didn't exactly comb carefully over the massive amount of data.

I'm not sure which version of uTorrent began this problem, but I've had this issue for one to two weeks, by my estimate. I didn't realize what was going on at first, and just thought I'd inadvertently filled up my drive myself at the time, so it's hard to pinpoint when this started and what version it started with.

I'm wondering if there's a way to shut off this logging, and also why the files are showing up in Mozilla and Windows paths? Thanks for any clues!

----

Edit: Found this, a more recent build that's supposed to fix this: http://forum.utorrent.com/viewtopic.php?pid=542476

My uTorrent "check updates" says no updates are available even though this new build was released 10 days ago. Odd. Trying a manual install, I'm assuming this will take care of the issue. Will report back.

----

So far so good. Had to manually delete the existing log files, but the issue seems to be resolved.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...