Jump to content

uTorrent crashes for no apparent reason


alen1989

Recommended Posts

Are there any crashlogs in $HOME/Library/Logs/CrashReporter? If so, can you zip them up and stick them on mediafire/something similar? (Unless theres only one log, then just put it on pastebin and link to it here).

This way, the devs will know exactly what caused it in your situation and it will be easier for the devs to fix then just guessing where the crash is randomly.

Link to comment
Share on other sites

There's actually no crashlog regarding uTorrent. I don't really know if it is important, but when other apps (which crashlogs are in there), there is a pop-up message about app crashing, but when uTorrent crashes, it just dies. Sometimes I don't even notice it, until I want to check download progress. Is there any other way to find out why this may be happening?

Link to comment
Share on other sites

Well, there is something regarding uTorrent, but it's only from yesterday/today (it didn't crash yet). I'll wait 'till it crashes again and if something new comes up, i'll be posting it here. Thanks for the help :)

Edit:

It just happened and what I got in console was:

12/6/08 10:54:35 AM com.apple.launchd[75] ([0x0-0x259259].com.bittorrent.uTorrent[21287]) Exited abnormally: Broken pipe

Link to comment
Share on other sites

  • 3 weeks later...

I am having the same issue but no error comes up. In 10 minutes time the app just closes subtly. Actually saw it fade away on my dock. No crash logs either. Using the newest 0.9.0.4. It wouldn't be a huge issue if I had to restart it ever now and then but then it runs the verify check for my files and it takes forever. But at least the app is now on mac :)

Link to comment
Share on other sites

  • 4 weeks later...

Same here on Leopard 10.5.6 with µTorrent 0.9.0.4. Same "Broken Pipe" message in the console.

I is almost systematic. µTorrent won't run for more thant an hour most of the time. Sometimes it runs longer, for no apparent reason neither. I'm downloading a 10GB torrent, maybe it has to do with memory management? I have to try to see if it also happens when only small torrents are downloading.

Link to comment
Share on other sites

At first sight I thought it could have something to do with your accounts running. Run as an admin with full rights or not - I wouldn`t except it right now until I´m rebuted ;) It has something to do with memory of course. Something causes uTorrent to break. Are there any more details in your logs? Before or after uTorrent has stopped from working? It means it couldn`t finish due to some other abortion or early finalization. That`s a broken pipe.

What`s your Mac`s equipment and how much data are you using the time your "pipe get`s broken?"

2.8Ghz | 2GB | 320GB | 10.5.6 -> runs perfectly with 13GB of data right now (my maximum was about 30GB at all)

Link to comment
Share on other sites

2.6GHz | 10.5.6 | 4GB | 160GB and I had about 20GB of data I think at that time (which was my maximum). I was also working on pictures with aperture, with a 30GB picture library, so it is very possible that there is a memory problem when there is a lot of paging, you're right indeed.

Link to comment
Share on other sites

  • 2 weeks later...

Yep getting the same thing.

Though i only have utorrent runnig, and maybe safari.

Have noticed that if you minmise (not hide)

there is a good chance it will crash within a few minutes, but not every time.

No crash logs, apart from the 1 line in the console...

Current crash has only 2 torrents with about 1gig of data in total.

MBP 2.5Ghz | 10.5.6 | 4GB | 250GB

31/01/09 2:08:34 AM com.apple.launchd[116] ([0x0-0x415415].com.bittorrent.uTorrent[7215]) Exited abnormally: Broken pipe

31/01/09 9:14:23 AM com.apple.launchd[116] ([0x0-0x454454].com.bittorrent.uTorrent[7752]) Exited abnormally: Broken pipe

2/02/09 3:06:52 AM com.apple.launchd[116] ([0x0-0x617617].com.bittorrent.uTorrent[11756]) Exited abnormally: Broken pipe

Link to comment
Share on other sites

Are you using external drives such as a USB HDD? Or did you have a look at your energy saving options (assuming that the MacBooks are quite efficient at saving energy due to disk sleeping mode, f.e.)

Try to turn off your hard disk sleeping mode or try to run uTorrent without your externals...

If it`s not due to some special system settings while trying to read/write, then it has to be a minor bug, for sure.

EDIT: I just got another clue which refers to the total number of your connections. Are they adapted to your kind of connection or do you have an abnormal high number of maximum/per torrent connections?

Link to comment
Share on other sites

no external drive.

i use the power savings options to wake the mac up at 2am (off peak quota time ) you can see one of the crashes happened a few minutes after the mac woke up.

Torrents are limited to 500 connections, each max 2000 global. only had 2 running at the time

31/01/09 2:08:34 AM com.apple.launchd[116] ([0x0-0x415415].com.bittorrent.uTorrent[7215]) Exited abnormally: Broken pipe

Though ive had it crash just opening the application... seems to happen more often if i minimise the application.

Link to comment
Share on other sites

I noticed that either it crashes within a few minutes, or it stay stable forever. And it definitely has something to do with either the number of connections or the size of the total torrent downloaded: when I have many big torrents, it crashes. When I have only one torrent, never.

Link to comment
Share on other sites

  • 2 weeks later...

I've started getting the application disappearing. I thought it was because I installed 091, but I can't say for sure. I did a full uninstall and then installed 090, and it still does it. The only pref I changed in 090 after installing it was the port to forward, the rest are default. I've tried a few different torrents, one at a time, it makes no difference. The app window just disappears with no crash dialog. Below is the result in my console window, as you can see it doesn't run for very long. Please help, this was working so well before.

22/02/09 4:59:43 PM uTorrent[6919] Could not find image named 'SplitViewGrabber'.

22/02/09 4:59:43 PM uTorrent[6919] Could not find image named 'HideStats'.

22/02/09 4:59:43 PM uTorrent[6919] Could not find image named 'ShowStats.tiff'.

22/02/09 4:59:44 PM uTorrent[6919] **** Posting Msg: BitTorrent_TorrentFileAdded ****

22/02/09 4:59:44 PM uTorrent[6919] *** _networkReachabilityChangedCallback got flags: -r-----

22/02/09 4:59:44 PM uTorrent[6919] networkReachabilityDidChange: NSConcreteNotification 0x1891a320 {name = BitTorrentNetworkReachabilityDidChangeNotification; object = 1}

22/02/09 4:59:44 PM uTorrent[6919] Show All Torrents

22/02/09 4:59:58 PM com.apple.launchd[121] ([0x0-0x135135].com.bittorrent.uTorrent[6919]) Exited abnormally: Broken pipe

Link to comment
Share on other sites

  • 3 months later...
  • 3 weeks later...
  • 4 months later...

I am having the same problem with the same type of error message from the console:

11/7/09 5.43.05 AM com.apple.launchd[176] ([0x0-0x13b13b].com.bittorrent.uTorrent[68325]) Exited abnormally: Broken pipe

I'm running a MacBook Pro with 1.5 GB of RAM, all of which is being used by various programs in addition to uTorrent.

Is it possible that this problem is fixed in the alpha version? Has anyone had better luck with the alpha?

Link to comment
Share on other sites

  • 1 month later...

I have experienced this 'silent' crashing half a dozen times on uTorrent version 0.9.3 (17496) for the Mac. This can happen anywhere between 1 and 8 hours I have experienced.

On several occasions I have had nothing but uTorrent open using my Macbook Pro (2.5 GHz Intel Core 2 Duo, 4 GB 667 MHz DDR2 DSRAM, Mac OS X Version 10.5.8) and it was close itself without warning. This is a clean install of OS X, and the uTorrent install is a clean install (not moving any files) but I did use the automated upgrade service a couple of days ago.

One thing I did notice in Console.app is the following repeated over and over again just before the crash:

10/12/2009 01:31:58 uTorrent[802] Fetching of url https://trackhub.appspot.com/announce?info_hash=H%16C%d5o%87%1b%3f%ceub%8a%e2%adn%f6WB%d5%d2&peer_id=-UM093B-XD%bd%1fHO%eew%d0F%b6%f2&port=12345&uploaded=180224&downloaded=0&left=4356911234&corrupt=0&key=5BFF5789&numwant=200&compact=1&no_peer_id=1&ipv6=fe80%3a%3a21f%3a5bff%3afec8%3aae5a failed, desc=Operation could not be completed. (com.google.mactoolbox.HTTPStatus error 503.), reason=(null)

This was repeated constantly and then:

10/12/2009 01:32:00 com.apple.launchd[400] ([0x0-0x39039].com.bittorrent.uTorrent[802]) Exited with exit code: 1

Could this be related to erroneous trackers being pinged perhaps?

Link to comment
Share on other sites

horrible time w/ utorrent as of late. no version works for me. here's what i'm getting with latest 0.9.2 build:

12/11/09 10:49:47 AM uTorrent[5257] Could not find image named 'SplitViewGrabber'.

12/11/09 10:49:47 AM uTorrent[5257] Could not find image named 'SplitViewGrabber'.

12/11/09 10:49:47 AM uTorrent[5257] Could not find image named 'HideStats'.

12/11/09 10:49:47 AM uTorrent[5257] Could not find image named 'ShowStats.tiff'.

12/11/09 10:49:48 AM uTorrent[5257] *** _networkReachabilityChangedCallback got flags: -r-----

12/11/09 10:49:48 AM uTorrent[5257] networkReachabilityDidChange: NSConcreteNotification 0x15c57140 {name = BitTorrentNetworkReachabilityDidChangeNotification; object = 1}

12/11/09 10:49:48 AM uTorrent[5257] networkReachabilityDidChange: NSConcreteNotification 0x15c57140 {name = BitTorrentNetworkReachabilityDidChangeNotification; object = 1}

12/11/09 10:49:48 AM uTorrent[5257] networkReachabilityDidChange: NSConcreteNotification 0x15c57140 {name = BitTorrentNetworkReachabilityDidChangeNotification; object = 1}

12/11/09 10:50:17 AM [0x0-0x1cd1cd].com.bittorrent.uTorrent[5257] uTorrent(5257,0xb0147000) malloc: *** mmap(size=688750592) failed (error code=12)

12/11/09 10:50:17 AM [0x0-0x1cd1cd].com.bittorrent.uTorrent[5257] *** error: can't allocate region

12/11/09 10:50:17 AM [0x0-0x1cd1cd].com.bittorrent.uTorrent[5257] *** set a breakpoint in malloc_error_break to debug

12/11/09 10:50:17 AM [0x0-0x1cd1cd].com.bittorrent.uTorrent[5257] *** set a breakpoint in malloc_error_break to debug

12/11/09 10:50:23 AM com.apple.launchd[149] ([0x0-0x1cd1cd].com.bittorrent.uTorrent[5257]) Exited abnormally: Abort trap

Link to comment
Share on other sites

Same here, really annoying.

OSX Snow Leopard 10.6.2 on iMac, uTorrent 0.9.3 Build 17496, random crashes, no Crash Reporter Log, in Console some GUI Errors (Sidebar is empty after restart of app etc.)

Sad, that uTorrent has this, strange is, that for a day or two after installation the app ran pretty smooth. Now I can not start it to run overnight, since it most likely crashes sometimes in the night with no log.

Come on guys, I have been really an uTorrent User on Win for several years, I would love to use the Mac Version on a day to day basis, but there is just no point, it is still an unreliable, unstable application.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...