osm0sis

Established Members
  • Content Count

    808
  • Joined

  • Last visited

Posts posted by osm0sis


  1. I have them documented, does that count ?

    I'm just sayin it may have been a bit premature to release this to stable.

    I understand that users here have the option to test the alphas, betas, etc. and report what they find but how about the devs?

    Yup.. welcome to the post-BitTorrent acquisition µTorrent, where meeting the release schedule (regardless of stability) and monetization are more important than bugs from 10 years ago.

    They've been releasing and forgetting about outstanding bugs for several releases now, so I'm sure it's become impossible for them to track a lot of them now that they've been building on top of them for awhile.

    I maintained a huge list of bugs for a few versions too. Largely ignored, of course, so I've given up.


  2. Is there any chance for the "Create Subdirectory" checkbox to save it's state, and doesn't always reset itself to checked? I kinda never create any subdirectories, so it would be nice if this checkbox could remember it's last state.

    Even an option in the Preferences / Advanced list - like "gui.create_subfolder_default" (false/true) - could do the trick.

    YES!

  3. Still makes it kaboom, but the disk cache is actually able to catch up in this version where it would just get stuck before, so... half way fixed?

    http://i.imgur.com/vFIG2.jpg

    You can see the gap in the graph before the disk writes start occurring. In that time the cache had exceeded its bounds (32mb) for a total of 140mb or so. It only does this with that overhead option enabled, as I've been saying since... oh.. 3.0. ;)

    So far I haven't seen the upload exceed my global limit (90). I'll continue to test though.


  4. "Apply rate limit to transport overhead" still breaks EEEVVERYTHING to do with the disk cache. This is a longstanding bug, if you don't plan on fixing it then just remove the option. It would be the responsible developer thing to do rather than leave broken settings in for versions and versions. ;)

    Also please make "Create subfo(lder)" remember its state. Every time the window pops up I have to uncheck it again since that's usually the way I want it. Thanks. :)


  5. --2012-11-21: Version 3.3 alpha (build 28582)

    - Fix UT Plus LREC height mis-sizing

    - Remove: obsolete graphic images

    - Fix: Crash in LAdWindow

    - Fix: Restore global upload rate limiting

    - Fix: rare crash in udp tracker code

    - Fix: coalesce writes from cache to disk

    Now we're talkin'! Thanks devs. Keep it coming. :D

  6. Torrents not getting removed from %AppData%\uTorrent seems slightly improved.. I think it might depend on whether its multiple torrents at once being removed from the list or if its just a single.

    Also, Cancel being the new default on the single removal dialog is annoying, please change it back.


  7. Global Upload speed limit still seems broken, but I think I know why. Setting the per-torrent limit works, and normally when you don't have a per-torrent limit set it shows as "unlimited" - SO, the reason global is likely broken is because of a derp in the code where per-torrent limit ALWAYS preempts Global, even though it should only override when set, or maybe not at all and always be a subset of Global. Setting bandwidth usage on the torrents to Low might also help.

    Edit: Nevermind... can't seem to reproduce this on a regular basis, or at least it still spikes to way above the global limit. :/

    Please do fix the bug though. It's a huge usability issue in the alpha at the moment.


  8. Just noticed the alpha doesn't seem to be respecting gui.default_del_action anymore. I have it set to 1 (Remove and delete .torrent) but my %AppData%\uTorrent folder is still filling up with files.

    Edit: Seems to be because some of them are/stay locked?


  9. Alpha doesn't handle a "." in the Name field either, breaks my usage case for a LOT of multifile torrents where I only really want 1 or 2 files.

    Apply rate limit to overhead still allows the disk cache to exceed its limit massively and pretty much all the bugs in my buglist from 3.1 are still valid.


  10. -- 2012-07-30: Version 3.2 (build 27636)

    - Feature: disallow http connections to tracker.openbittorrent.com and tracker.publicbt.com

    Interesting. Why this change? Especially considering neither of these trackers has worked at all for me (http or udp) for the last week or so.. Roughly since Demonoid went down.