Active torrent limit ignored

[Vorthod]

Can somebody explain this to me? I've attached an image that shows my problem, but i will explain it here anyway. Some nights i wake up to find that uTorrent had not been seeding overnight and every unfinished torrent is trying to run at the same time despite the fact that i only allow 5 active torrents at once. the most annoying part is that not a single torrent is actually doing any seeding.
The only way i have found to fix this is to restart the program entirely, which brings me to a second issue. Normally uTorrent shuts down fine, but after this error happens, the uTorrent process will remain active even though it's program ID, toolbar thumbnail, and taskbar icon have all disappeared. Trying to start the program again essentially is a No-op until i go into the task manager and kill the process directly (at which point i can start the program again without issue)

In case it matters, I run a transfer cap on uploads that usually caps out my seeding after a few hours. I also use the scheduler, but on this most recent instance of the issue, none of the scheduled downtimes were anywhere near the time of the error (scheduler breaks certain times Mon-Thurs, and this happened around midnight on friday)

[DreadWingKnight]

A bunch of torrents that aren't counting towards the limit because they aren't transferring.

[Vorthod]

okay...but the question is why is that happening and how can i fix it? and why does it cause the weird memory leak or whatever that causes the process to remain open after the program has shut down? Normally my torrents just show up as "queued seed" but when they get like this the entire program just stops (downloads too).

[DreadWingKnight]

It's happening because your queue.dont_count_slow_ entries are set to the default

[Vorthod]

thank you. i have turned those two entries to false and will see if i end up getting problems.

[Audisek]

It might not be seeding because they are strongly everseeded and there are no peers.
And why do you limit your seeding in the first place? I Force Start all my torrents so I can feel like I am useful after I seed 50GB a day.

[Vorthod]

Before the transfer cap is reached on a non-glitch day, the torrents are able to find peers to upload to before i even wake up. the seeding also properly restarts after i reboot uTorrent to drop that glitch. so there is surely a problem in the client, not the swarm itself.

as for why i limit, my ISP gets ticked at me when i upload too much in conjunction with my already heavy internet use as well as the fact that I'm sharing private internet with three other people in my house. The last time i went for a few months without a transfer cap, our internet slowed down tremendously for the rest of the year. (and before you ask, yes i turned off the torrents when i tried to do anything internet heavy. they were not hogging bandwidth when i was measuring my internet speed)

 

As for the glitch in question, it has not returned since i modified the advanced settings as mentioned above. It may only have been four days ago, but these are promising results