AdamK

Here is what the uTorrent team would like to do in the near future: Add the ability to make some problem reports and viewing the changelog into the client itself. We don't have the system we need to do this yet.

Here you go: http://forum.utorrent.com/viewtopic.php?pid=766512#p766512

Can you describe your reproduction steps? Are you able to reproduce this with default settings?

-- 2013-12-24: Version 3.4 (build 30444) RC3 - Fix: Installer issue when going from 3.3.1 or before to 3.3.2 or later: infinite mutex wait - Performance Fix: Main Torrent listview should update only when needed - Fix: Installation issue: Run at startup not set - Fix: The information of deselected torrent remained in the tabs area - Change: Remove [x] next to Ads - Fix: restore crash count information - Change: Write more aggressively when coalesced pieces exist in cache - Possible fix for netprofm.dll related crash, appearing after MS patch to IE 10

-- 2013-12-18: Version 3.4 (build 30429) RC2 - Fix: Incorrect text color (black) when highlighted (dark blue) on XP - Change: point initial page for fresh install to bundles.utorrent.com (nee /current/index.html) - Fix: Bug affecting Plus customers - Feature: Add BitTorrent Labs icon to the status bar - Fix: Bug in categorizing torrents may lead to some missing in UI Download the new version now!

Does this magnet link work? magnet:?xt=urn:btih:E3811B9539CACFF680E418124272177C47477157&dn=ubuntu-13.10-desktop-amd64.iso&tr=http%3a%2f%2ftorrent.ubuntu.com%3a6969%2fannounce&tr=http%3a%2f%2fipv6.torrent.ubuntu.com%3a6969%2fannounce

Thanks - I just accepted a patch for that a few hours ago. That fix will be out today.

On a RC???? No' date=' not on an RC. The beta track works that way currently, but there is only one RC at a time. [url']http://download-lb.utorrent.com/endpoint/utorrent/os/windows/track/beta http://download-lb.utorrent.com/endpoint/utorrent/os/windows/track/rc Still present in build 30379 Last working 30304 but not on 30300. Still present in build 30428' date=' fix it please.[/quote'] Thanks for giving the version numbers, that will help a lot.

Yep, we're working on the high-CPU issue, and we have it reproduced here. Once we isolate the cause, we can assess how complex the fix will be. The over-eager disc-overload message is probably going to be a bit more tricky, but we'll see.

That is hilarious! Don't worry, we are almost finished coming up with a plan for releasing features, that I think we'll all be happy with. Once I get everyone at the office to review it, I'll post it here for all the testers, as well. (I'm hoping to get started in January). I think it will take us about a month to do, once we start. AdamK

Hi everyone, thanks for pointing this out - we tracked it down to overflow in a 16-bit counter used to determine when to send performance/usage data (e.g. How often do users use the RSS feature vs. the Add Torrent feature)

Changelog: Note that you will occasionally see other versions being served from the download link. These are builds to test special bug-fixes or features that are not yet battle-tested -- 2013-12-16: Version 3.4 (build 30428) RC1 - Fix: .torrent association problem during install on Windows 8 and later - Feature: Add BitTorrent Labs icon to the status bar - Feature: Add Help menu items for bundle and BitTorrent Labs - Fix: Toolbar buttons are not activated after adding torrents - Change: Default button in delete torrent dialog is now [OK] - Fix: Firewall issue if running client from downloaded folder - Change: Implement bundle badging - Change: Implement bundle unlock toolbar - Change: Implement bundle unlock right click menu - Change: Implement bundle history tab - Fix: MON-3: Search icons not showing when client first starts - Change: Highlight the last newly added torrent - Fix: Toolbar buttons are not activated after torrents are selected - Feature: ADS-138: Change logging in settings to remove OpenX - Feature: ADS-176: Keyboard shortcut to refresh ads now - Feature: ADS-33: Overlay image when "i" is moused over - Feature: ADS-35: Custom PDD

Thanks for your feedback. I think giving a full changelog for the test versions as well is a good idea. Two main problems we'd like to solve: * Don't expose more users than necessary to bad versions * get new revisions in front of users as quickly as possible (These versions may be developed in parallel)

Hi - Thanks for your dumps for 30345. That issue seems to be fixed in the next version. Could you give that a try? http://tinyurl.com/orarlep