Firon Posted May 7, 2009 Report Share Posted May 7, 2009 µTorrent Mac 0.9.1.2 is out now.The network code has been overhauled to fix high CPU problems and connectivity issues. Many crashes have been fixed.Download it here! http://utorrent.com/downloads/macChanges in 0.9.1.2 * Fix: Socket bug that caused upnp to hang and fail and hung shutdown. * Fix: Shutdown timeout. * Fix: Socket error that caused occasional 100% CPU on TCP sockets * Fix: Bad socket state on UDP socket timeout that randomly caused high CPU usage * Fix: Various TCP and uTP fixes and optimizations. * Fix: Optimization for uTP rate limiting. * Fix: uTP rate limiting bug. * Fix: Broken search. * Fix: Copyright notice. Link to comment Share on other sites More sharing options...
fcjvisser Posted May 8, 2009 Report Share Posted May 8, 2009 Thank you this release is fantastic - the only thing i needed to sort was my port number and and then set the rule in my router.I am connectable with this release as i wasn't with the 2 after 0.9.0.4 - cheers for all the great work you have done with this clienti love it!!!!!! Link to comment Share on other sites More sharing options...
Nahvi Posted May 8, 2009 Report Share Posted May 8, 2009 Looks good, no glitches that I've noticed so far. Link to comment Share on other sites More sharing options...
antikorr Posted May 8, 2009 Report Share Posted May 8, 2009 Works smooth like a ninja blade. Yay! Thanks alot for the release!!!! Link to comment Share on other sites More sharing options...
PeeWeeGee Posted May 8, 2009 Report Share Posted May 8, 2009 Build either crashes or cripples my system (basically stock) 100% of the time upon launch. Something is MAJORLY wrong. Everything was smooth before this version. :-(edit: In fact, indications point to 100% CPU usage. Pref and dat files were cleared out. Application still crashes at launch.PWG Link to comment Share on other sites More sharing options...
theron Posted May 8, 2009 Report Share Posted May 8, 2009 Interesting PWG. Tell me more about your system (eg: OS version/build, CPU stats, memory, etc.) If you can take a snapshot of the process when it's misbehaving and send that to me that would be very helpful too. I'd like to reproduce the problem so we can fix it. Thanks.-T Link to comment Share on other sites More sharing options...
Thrash911 Posted May 8, 2009 Report Share Posted May 8, 2009 Whoo! You guys do a great job! This release is working like a charm. But like 'fcjvisser' also mentioned, I had to re-set the port number (it went to zero, after updating). But after that was done, everything worked fine, and still is!Thanks a lot, and keep up the great work. Much appreciated!:-) Link to comment Share on other sites More sharing options...
NoOneButMe Posted May 8, 2009 Report Share Posted May 8, 2009 @PeeWeeGee: "snapshot" means "Hit "Sample" in Activity monitor and pastebin it then link it to here to read" Link to comment Share on other sites More sharing options...
hl2run Posted May 9, 2009 Report Share Posted May 9, 2009 Working like a charm http://dl.getdropbox.com/u/3872/utorent92.png Link to comment Share on other sites More sharing options...
PeeWeeGee Posted May 9, 2009 Report Share Posted May 9, 2009 All - First, thanks for the replies and interest. The only problem I have is that the system becomes SO crippled that it is an arduous task to get ANYTHING captured for review. But I let the launch continue for 15 minutes or so and this is what I could get:Sampling process 2325 for 3 seconds with 1 millisecond of run time between samplesSampling completed, processing symbols...Analysis of sampling uTorrent (pid 2325) every 1 millisecondCall graph: 2131 Thread_2503 2131 0x2126 2131 NSApplicationMain 2131 -[NSApplication run] 2131 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] 2131 _DPSNextEvent 2131 AEProcessAppleEvent 2131 aeProcessAppleEvent 2131 dispatchEventAndSendReply(AEDesc const*, AEDesc*) 2131 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) 2131 _NSAppleEventManagerGenericHandler 2131 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] 2131 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] 2131 -[NSApplication(NSAppleEventHandling) _handleAEOpen:] 2131 -[NSApplication _sendFinishLaunchingNotification] 2131 -[NSApplication _postDidFinishNotification] 2131 -[NSNotificationCenter postNotificationName:object:] 2131 -[NSNotificationCenter postNotificationName:object:userInfo:] 2131 _CFXNotificationPostNotification 2131 __CFXNotificationPost 2131 _nsnote_callback 2131 0x3f21 2131 -[NSWindow makeKeyAndOrderFront:] 2131 -[NSWindow orderWindow:relativeTo:] 2131 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] 2131 -[NSWindow displayIfNeeded] 2131 -[NSView displayIfNeeded] 2131 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] 2131 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] 2131 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] 2131 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 2131 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 2131 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 2131 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 2131 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 2131 -[NSView _drawRect:clip:] 2131 -[NSControl drawRect:] 2131 -[NSButtonCell drawInteriorWithFrame:inView:] 2131 -[NSButtonCell _configureAndDrawTitleWithRect:cellFrame:controlView:] 2131 -[NSButtonCell titleRectForBounds:] 2131 -[NSButtonCell(NSButtonCellPrivate) _centerTitle:inRect:] 2131 -[NSAttributedString(NSStringDrawingExtension) _sizeWithSize:] 2131 -[NSAttributedString(NSExtendedStringDrawing) boundingRectWithSize:options:] 2131 __NSCreateRenderingContextForAttributedString 2131 -[NSMutableAttributedString(NSMutableAttributedStringKitAdditions) fixAttributesInRange:] 2131 -[NSMutableAttributedString(NSMutableAttributedStringKitAdditions) fixFontAttributeInRange:] 2131 +[NSFont coveredCharacterCache] 2131 ATSFontGetUnicodeCharacterCoverage 2131 _eATSFontGetUnicodeCharacterCoverage 2131 FOGetCoveredUnicodeChars 2131 SendGetFCacheDataMessage 2131 SendFontManagementMessage 2131 SendFontManagementMessageWithMessageStatus 2131 ReconnectToATSServer(int, unsigned char, unsigned char) 2131 RendezvousWithServer(unsigned long, char*) 2131 SendFontManagementMessage 2131 SendFontManagementMessageWithMessageStatus 2131 mach_msg 2131 mach_msg_trap 2131 mach_msg_trap 2131 Thread_2603 2131 thread_start 2131 _pthread_start 2131 0x58cf0 2131 mach_msg 2131 mach_msg_trap 2131 mach_msg_trap 2131 Thread_2703 2131 thread_start 2131 _pthread_start 2131 __NSThread__main__ 2131 -[NSThread main] 2131 0x6c90a 2131 0x56050 2131 0x3117c 2131 0x3120b 2131 0x311bd 2131 0x28714 2131 pthread_cond_timedwait$UNIX2003 2131 __semwait_signal 2131 __semwait_signal 2131 Thread_2803 2131 thread_start 2131 _pthread_start 2131 0x27c6a 2131 0x28714 2131 pthread_cond_timedwait$UNIX2003 2131 __semwait_signal 2131 __semwait_signal 2131 Thread_2903 2131 thread_start 2131 _pthread_start 2131 0x293d3 2131 0x28714 2131 pthread_cond_timedwait$UNIX2003 2131 __semwait_signal 2131 __semwait_signal 2131 Thread_2a03 2131 thread_start 2131 _pthread_start 2131 0x36f05 2130 0x36d80 2128 kevent 2128 kevent 2 0x36d80 1 0x36d87 1 0x36d87Total number in stack (recursive counted multiple, when >=5): 5 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 5 _pthread_start 5 thread_startSort by top of stack, same collapsed (when >= 5): __semwait_signal 6393 mach_msg_trap 4262 kevent 2128Sample analysis of process 2325 written to file /dev/stdoutAfter which, the app had _still_ not completed a full launch and my ability to do much else was greatly hampered.SYSTEM SPECS: Model Name: Mac Pro Model Identifier: MacPro3,1 Processor Name: Quad-Core Intel Xeon Processor Speed: 2.8 GHz Number Of Processors: 2 Total Number Of Cores: 8 L2 Cache (per processor): 12 MB Memory: 4 GB Bus Speed: 1.6 GHz Boot ROM Version: MP31.006C.B05 SMC Version: 1.25f4 OS Version: 10.5.6Hope this helps. The app is on its way to be something stellar!PWG Link to comment Share on other sites More sharing options...
NoOneButMe Posted May 9, 2009 Report Share Posted May 9, 2009 @PeeWeeGee: What process is using up all your CPU's? Positive its uTorrent? O.o Can you try moving your preferences (~/Library/Preferences/com.Bittorrent.utorrent.plist and ~/Library/Application Support/uTorrent) to your desktop and then restarting uTorrent again?Not related to uTorrent, but a hunch I'm having: Open Font Book (/Applications/Font Book), Select All Fonts, then Select all the fonts in the list (click on one and cmd + a) and then select File -> Validate Fonts. If a font is invalid, it *might* be the cause of your CPU being eaten up. Link to comment Share on other sites More sharing options...
PeeWeeGee Posted May 9, 2009 Report Share Posted May 9, 2009 He shoots, he SCORES!@NoOneButMe: Good hunch. There were some corrupt fonts and I suspect they are the culprit. (They are SYSTEM FONTS! wtf?!) Anyway, thanks for the tip! I'll get this all sorted out and give an ACCURATE bit of feedback on the APP! ;-)Regards,PWG Link to comment Share on other sites More sharing options...
hl2run Posted May 9, 2009 Report Share Posted May 9, 2009 After a few hours of seeding uTorrent eats up 100% Link to comment Share on other sites More sharing options...
NoOneButMe Posted May 10, 2009 Report Share Posted May 10, 2009 @hl2run: Can you take a sample and post it please? See above for instructions. Link to comment Share on other sites More sharing options...
hl2run Posted May 10, 2009 Report Share Posted May 10, 2009 It happened just once, therefore I can't give you a sample yet Link to comment Share on other sites More sharing options...
PeeWeeGee Posted May 10, 2009 Report Share Posted May 10, 2009 Just an update... After reinstalling the OS (10.5.6) to restore all operating files, utorrent seems to be running perfectly. In fact, this is the first build where I've been able to get a "green" connection working indication!Cheers,PWG Link to comment Share on other sites More sharing options...
Sanctuaryu Posted May 10, 2009 Report Share Posted May 10, 2009 Downloaded 0.9.1.2 and experiencing occasional 100% CPU usage issue. Here's the sample http://pastebin.com/m635a274cRuns at 100% for a minute or two, then back to normal. (however I've also noticed this version to be using more CPU in than 0.9.1 I was using prior - 6-9% vs 4-5%... why is that?)2006 MacBook Core 2 Duo 2 GHz, 10.5.6, uTorrent 0.9.1.2. Link to comment Share on other sites More sharing options...
hl2run Posted May 10, 2009 Report Share Posted May 10, 2009 Here's my sample http://dl.getdropbox.com/u/3872/SampleofuTorrent.txtIt happened when I was just seeding.And It's kinda true that in normal use uTorrent is using more CPU than before.But keep up the good work. Link to comment Share on other sites More sharing options...
fcjvisser Posted May 10, 2009 Report Share Posted May 10, 2009 i have now a port issue which i have posted in the trouble shooting section - seems to be randomizing even though i have not set it to do so. Link to comment Share on other sites More sharing options...
Pai Posted May 10, 2009 Report Share Posted May 10, 2009 Just updated, port was 0 after update so I set the correct one and restared. After that, port was always randomized on restart. Removed preferences, restarted again, same thing. When I set a random port the connection status is not available, but when I set the correct port and press <Enter> the status is changed *instantly* to "Listen Error".Same problem as previous builds ? I'm on 10.5.6, MBP 2.4 GHz 4GB lots of free HDD.edit: just downgraded, and port is working as expected on previous build (0.9.0.4, last one that worked correctly for me) Link to comment Share on other sites More sharing options...
fcjvisser Posted May 11, 2009 Report Share Posted May 11, 2009 yes it does seem as though the port problem is still around the only build that has worked perfectly for me is 0.9.0.4 as well - but with that one you cant select files for d/l , so i will stick with this latest build for a bit and see what happens with the ports - but if it is too much of a hassle trying to reset port numbers each time i restart utorrent, then i will down grade to 0.9.0.4 again.Hope fully this port problem will get sortedcheers for all the good work Link to comment Share on other sites More sharing options...
dreamsandbones Posted May 11, 2009 Report Share Posted May 11, 2009 Hi. Tried to update uTorrent but ultimately failed, now it won't open. The error message I'm getting is that the application quit unexpectedly. The crash report: Process: uTorrent [254]Path: /Applications/uTorrent.app/Contents/MacOS/uTorrentIdentifier: com.bittorrent.uTorrentVersion: ??? (???)Code Type: X86 (Native)Parent Process: launchd [154]Date/Time: 2009-05-11 20:10:48.505 +0200OS Version: Mac OS X 10.5.6 (9G55)Report Version: 6Exception Type: EXC_BREAKPOINT (SIGTRAP)Exception Codes: 0x0000000000000002, 0x0000000000000000Crashed Thread: 0Dyld Error Message: Library not loaded: @loader_path/../Frameworks/Sparkle.framework/Versions/A/Sparkle Referenced from: /Applications/uTorrent.app/Contents/MacOS/uTorrent Reason: Incompatible library version: uTorrent requires version 1.5.0 or later, but Sparkle provides version 1.0.0 Link to comment Share on other sites More sharing options...
NoOneButMe Posted May 11, 2009 Report Share Posted May 11, 2009 @dreamsandbones: redownload uTorrent from http://www.utorrent.com/downloads/mac Link to comment Share on other sites More sharing options...
dreamsandbones Posted May 12, 2009 Report Share Posted May 12, 2009 Great, that worked!Thanks! Link to comment Share on other sites More sharing options...
drpiety Posted May 12, 2009 Report Share Posted May 12, 2009 Is it only me the torrents do not stop seeding at the desired ratio? The Port stays stable for me now. CPU at 13%, no Peaks. Oh btw the Port is only OK since I ran applejack! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.