Jump to content

utorrent.exe*32 keeps running even after closing


seanincali

Recommended Posts

I close my utorrent and everything closes, but if i run task manager, you can see utorrent.exe*32 keeps running.

then restarting the utorrent doesn't work nor can I force quit the process. and process, nor end process tree seem to solve the problem. i have to restart the computer to quit it.

i'm on windows vista home premium. utorrent v 3.1.2.26773.

this started with the latest windows update i think. i don't recall having this problem ever.

Link to comment
Share on other sites

seanincall: You do not provide very much info. You do not say how many torrents you have that are active. uTorrent, on closing, notifiys trackers of your statistics on each active torrent. That takes time. And it could take a long time (or at least feels that way) when some of the trackers timeout. Try it with one torrent, and make sure the status of all trackers is "Working". See how long it takes. Killing the process will force a re-check the next time you start. If you have a large cache it make take some time to write out dirty blocks? But I think the issue is in the update tracker statistics. I run about 60 downloads and uTorrent always (well ok, usually) shutsdown in a about 1 min. But I try to remove all trackers where I get a consistent error (timeout, refused connection, etc.)

Link to comment
Share on other sites

  • 2 weeks later...
I close my utorrent and everything closes, but if i run task manager, you can see utorrent.exe*32 keeps running.

then restarting the utorrent doesn't work nor can I force quit the process. and process, nor end process tree seem to solve the problem. i have to restart the computer to quit it.

i'm on windows vista home premium. utorrent v 3.1.2.26773.

this started with the latest windows update i think. i don't recall having this problem ever.

I am having this same problem, one that a LOT of uTorrent users are having. The response "You do not provide very much info" appears to imply that this is a relatively new phenomenon that the uTorrent team is just hearing about and more info is needed to properly troubleshoot the issue.

Quite the contrary. This complaint (and another complaint about the re-checking process hanging and not checking anything) has been highlighted as a major issue for months and nothing has been done that I can see; certainly, nothing has been done when the response to another complaint about the same issue merits the response that "info is needed".

Just browse through prior postings. You'll get all of the info you need.

Link to comment
Share on other sites

Stating he did not provide enough info is valid. How many torrents did he have active? How many trackers for each torrent? Was the status all trackers working? Or was there some errors (timeout)? etc. etc. etc.

It has been posted before that when active torrents are stopped uTorrent notifies trackers of your current ratio. It must also close all open files cleanly. Killing the process will only force a Force -recheck on all active downloading torrents at the time you kill the process.

This problem may have been reported several times, but if you do not give developers enough information how can they recreate the problem?

Link to comment
Share on other sites

Stating he did not provide enough info is valid. How many torrents did he have active? How many trackers for each torrent? Was the status all trackers working? Or was there some errors (timeout)? etc. etc. etc.

It has been posted before that when active torrents are stopped uTorrent notifies trackers of your current ratio. It must also close all open files cleanly. Killing the process will only force a Force -recheck on all active downloading torrents at the time you kill the process.

This problem may have been reported several times, but if you do not give developers enough information how can they recreate the problem?

What you are not understanding is that the uTorrent process stays "open", with a FIXED amount of memory (in other words, it is "locked" up), for hours after closing the program via "exit". Without attempting to force the process to close via Task Manager, the process will stay open for hours. Further, after waiting for hours for the process to close, attempting to close the program by way of Task Manager doesn't work. The process is locked open, with a fixed amount of memory being used (always upwards of 500k of memory). uTorrent can't be closed.

it doesn't matter how many torrents I had open, nor how many trackers, nor what the status of all of the trackers. uTorrent refuses to close in the normal fashion.

If a uTorrent user needs to do something else other than attempt to close the program via "exit", then the program should come with instructions. However, most programs are "exited" when "exit" is clicked on.

Link to comment
Share on other sites

What you are not understanding is that the uTorrent process stays "open", with a FIXED amount of memory (in other words, it is "locked" up)

What YOU are not understanding is that the original poster didn't give ANY of the information that you did, so they didn't give enough information to actually identify the problem.

And if the cause of their issue isn't the same, then you thread hijacked.

Link to comment
Share on other sites

What you are not understanding is that the uTorrent process stays "open", with a FIXED amount of memory (in other words, it is "locked" up)

What YOU are not understanding is that the original poster didn't give ANY of the information that you did, so they didn't give enough information to actually identify the problem.

And if the cause of their issue isn't the same, then you thread hijacked.

How would I know if the cause is the same? I have a problem and I don't see a solution yet. And I didn't "thread hijacked". I just said "Me, too".

So, after all is said and done, what is the solution? BTW, if I had a link to download a previous version, that would be great.

Link to comment
Share on other sites

What's the size of your settings.dat file?
if I had a link to download a previous version, that would be great.

And if I had a brown note for every time I've told people we don't support that, I'd not be in debt (and THAT would be great).

And my "settings.dat" file is where?

BTW, is there someone else besides DreadWingKnight who is familiar with uTorrent who is able to respond? The responses I am getting from the poster aren't helpful at all. There are too many postings smacking me upside the head and not enough postings with complete information on how to solve the issue that a whole bunch of users have.

Link to comment
Share on other sites

And my "settings.dat" file is where?

%appdata%\utorrent

There are too many postings smacking me upside the head and not enough postings with complete information on how to solve the issue that a whole bunch of users have.

There are too many postings by people who don't even attempt to search or browse and instead just open a new thread or hijack someone else's to get help.

Link to comment
Share on other sites

And my "settings.dat" file is where?

%appdata%\utorrent

There are too many postings smacking me upside the head and not enough postings with complete information on how to solve the issue that a whole bunch of users have.

There are too many postings by people who don't even attempt to search or browse and instead just open a new thread or hijack someone else's to get help.

Again, inadequate information. Where do I find the settings.dat file? Where do I start to "drill" down to find it?

Link to comment
Share on other sites

Hang-up on exit seems to fix fixed in 3.2 - b 27113 . Check it up..

Any idea how I find that 27113 build? I don't see a way to get it on the products page. BTW, does this build fix the RAM issue, where uTorrent uses increasing amounts of RAM, often upwards of 1.5GB?

Link to comment
Share on other sites

It's a 3.2 build.

Any idea where to find it and does it fix the RAM "leaking" issue, too? (I hope that is the word that people are using to describe RAM increasing). My system is Windows 7, 64 bit, 4Gb of RAM. I am using McAfee anti-virus. BTW, i see where some users forward "logs" for review. I would be glad to do the same if I could be informed on where they are.

Thanks in advance.

Link to comment
Share on other sites

I am not aware of any high-memory-usage issues with the latest stable.

Hi: I am running the Alpha build and it behaves like earlier iterations re: memory. I have the cache set to 64MB. I have one torrent downloading. Disk overload is at 100%. I open Task Manager and watch the RAM used by uTorrent slowly climb. Doesn't stop, doesn't reverse. Just keeps slowly climbing. Of course, when you exit uTorrent, the process doesn't stop. I needed to reboot the PC to get it removed.

So, while it seems you guys are working hard to resolve the issues, which I very much appreciate, it appears the Alpha build has some of the same bugs.

I am running Windows 7, 64 bit, 4GB of ram.

Link to comment
Share on other sites

The alpha is just that - an alpha. :P

Use 3.2 instead.

Is utorrent.exe using the RAM, or is it just system RAM being used? Because if it's the latter, that's not a bug. That's just Windows doing caching.

3.2 has its own problems, which is why i was hoping that the Alpha release would work.

uTorrent.exe is using the RAM.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...