-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent freezes #1298
Comments
i think that it happens because it jumps back to the all torrents tab when you add more torrents and with hundreds or even thousands torrents getting and rendering the stats for all of them is a very heavy operation. this thing really needs a option that allows setting the default tab so that it never jumps back to the all torrents tab |
The program is written in Pascal and its maintenance is not an easy task. I found a simple way (as probably many).
works great. |
never seen any pascal code before but i guess that i could hardcode the things that i want. should not be too hard to figure out how to do it since something already defines the defaults |
I have the same issue but on archlinux. |
No offense, but that tells me some refactoring is due, regardless of this issue. |
Good luck. We dont mind. There are only 100,000 lines. Change the code. Check for changes. P.S. The code is not mine, so I will not take up this work, neither free nor paid. |
Any action that involves communication with the server may or may not cause the whole application to freeze for a moment or two. It may or may not go into "Not responding" mode. And it may or may not mess up its GUI while frozen. It also may or may not turn up a "Bad Request" error. Not all freezes result in this error, but this error always comes after a freeze - never on its own.
I understand that sometimes the application needs to wait for the server to respond, but for god's sake do it in the background, please. Or asynchronouly at least.
A side-effect of these freezes is that it may sometimes "miss" a torrent getting added, or some other action is missed. After it unfreezes, say, 20% or so of the time, the torrent/magnet I clicked is not added, regardless of whether I got that "Bad Request" error.
Another side-effect is that (sporadically though) a secondary instance of the program is launched, which is only adding more confusion. Which one is now the one catching clicks on magnets? One of the two, and it's always unluckily the one I decide close.
TL;DR
Please wait for server responses in the background or asynchronously. And keep a queue of actions to perform on the server, so that requested actions aren't lost.
Versions:
The text was updated successfully, but these errors were encountered: