![vuze has just uploaded an important update vuze has just uploaded an important update](https://s3.amazonaws.com/neowin/news/images/uploaded/2017/08/1501845008_mainwindow.jpg)
![vuze has just uploaded an important update vuze has just uploaded an important update](https://i1.wp.com/camerajabber.com/wp-content/uploads/2017/07/Vuze_camera_review_build.jpg)
and saying that the user needs to prove it is transmissions fault! Setting as wontfix instead since the intent seems to just close this : It is sad to see this bug is being hand-waived without actually giving us steps to debug the issue. Its just lack of interest in debugging from the transmission devs. No debug info was requested, so not incomplete. We are facing the bug and we have provided the info we can. If transmission devs dont want to fix the issue, it's up to you folk.īut mentioning it as an invalid bug is wrong.
![vuze has just uploaded an important update vuze has just uploaded an important update](https://cdn.neow.in/news/images/uploaded/2015/06/vuze.jpg)
Vuze does this very well, if we set a global limit then it *is* honored. How are other clients able to control this global transfer too? Then what is the purpose of having a global limit if it cannot control global transfer? The problem here is not the over-head, but why isnt transmission trying to control the overhead even when we explicitly set the global limits? If we knew about torrent protocols and if we knew how to debug, wouldnt we let you know already? There are screenshots of users facing the problem that is the info *we* can provide. Why dont you try to give us some steps to debug this issue? and then tell us its not transmission's fault! : It is sad to see this bug is being hand-waived without actually giving us steps to debug the issue.