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
[3.1.10] - Frequent UI hangs when downloading torrent #2003
Comments
I've the same problem. Tried completely reinstall, but not helping. |
Same issue here. Qbittorrent works and torrents are downloading but UI freezes randomly for about 5-20 sec. Tried reinstall... same problem. Win 7 64bits, SP1, no firewall. |
Do you see a cpu spike in that period? |
and are you using operating system caching? |
@chrishirst First time I thought this is the problem, but with/without the problem is appears/remains. @sledgehammer999 I couldn't see any (or a very very little, somebody else also check please). I have an old Dual-Core E5200 2,5GHz cpu. |
Yes that is the problem with this version. |
Just so you know I have no idea what causes this. I don't experience it on my system (Windows XP dual core, 1.5GB RAM). |
I have AMD Phenom II X4 B55 (Quad-core at 3.2Ghz) and 8GB of RAM. Cpu stays at ~5%-11% when UI hangs. I dont see any notorius spikes of cpu use neither of ram. |
What is the interval between the freezes? |
I dont have any RSS. Interval between freezes is: 5-7 secs working for me then it hangs for about 15~20 secs, then works then hangs. I disabled anti-virus and no help. I dont see anymore details i dont know how to help. Im going to try an older version for now. |
My experience is pretty much the same as nhasbun as well. Since you're not experiencing this sledge, it's probably related to Win7. |
I think that someone made mistake with waiting to long for announce the next version with overmuch changes and corrections so now it is imposible to spot the cause. |
At everyone: What happens if you downgrade to 3.1.9.2 ? Does this freeze still happen?
Does it still freeze? (I am wondering if this is an issue in the networking code) |
Sledge, removing all torrents will fix it, since as I said it only happens when something is downloading. Right now, I'm seeding some stuff. The freeze doesn't happen because nothing is downloading. But as soon as I add a new torrent to download, it will happen until it finishes. |
So only on downloading not on uploading, right? |
It happens with os cache disabled as well. |
OK I am waiting for someone to try with 3.1.9.2 so I can narrow it down. |
Problem happens with uTP disabled, DHT disabled, local discovery disabled, pex disabled, encryption disabled, os cache disabled. Happens too while seeding. Only stops when deleting all torrents. Downgraded to 3.1.8 and no problems. |
As I say: to much changes that could be discovered!! |
OK. I am building a v3.1.10 using the same version of libtorrent used in 3.1.9.2 to see if that is the problem. It will take a while to complete. @anyN don't worry there is a far quicker way of testing each change to find the culprit. All I need is you guys to test. What is the faster way? Let's say I made 20 changes. I do a build based on the first 10. (ie half of the total). If the problem persists I know that the rest 10 aren't the problem. Then I'll create a new build for the first 5 and test again. Each time excluding a huge chunk of commits. Then at worst after 4 or 5 tries I'll know which commit has the problem. |
v3.1.10 with libtorrent r9872(same as 3.1.9.2): http://builds.shiki.hu/temp/qbittorrent_v3.1.10_libtorent_r9872.7z |
problem solved for me ! |
Sorry not for me. qBittorrent version: v3.1.10
|
@anyN does it happen frequently? |
Well I suppose not frequently. Last sesion in the morning I did not get any crash but now imediatly. |
Not frequently I will say. In fact this was only one. But laging or delaying or shorttime hangig persist! |
Difference was pretty noticeable for me. Just going for a pretty disfunctional and tiltish menu navigation to zero lags-freezes. Im going to try it for more time anyways...keep running with a couple of torrents and going to tell later. PS: Im sorry but problem is still there. UI is hanging out again with same behavior than before. |
Problem still exists. |
@sledgehammer999 could we measure a time of each event handled by main loop and log all event that takes more then, say, 20 ms? http://stackoverflow.com/questions/15097861/qt-measure-event-handling-time |
Probably yes. It seems quite simple. However I cannot provide a build with this before weekend. I can only do builds based on the git commits atm. |
OK. In a couple hours I'll post builds depending on the commits chriskohlhoff mentioned. |
Here are 3 new builds for you guys to test: |
@chriskohlhoff Do you know of any tool that is easy for someone inexperienced to use? |
It looks like all of them is working fine. |
@junpet Can you test this final build? It should re-introduce the freeze. |
Just like you said. It's freezing like hell. |
@chriskohlhoff we have found the offending commit. It is boostorg/asio@0484963 . If/when you push a fix, please leave a message here so I can provide a test build and confirm. Btw, do I have to open a bug report to the official boost bug tracker? @ everyone else. I am closing this. Until a fix is provided, all future qBittorrent releases will use Boost 1.55, which doesn't have the freezing problem. Thank you all for your cooperation. |
Please raise a ticket if you can. However, it's currently a long way from having enough information for me to attack the problem. Does your program have some logging or tracing facility? If you do, it would be great if you could please instrument the function bodies of boost::asio::detail::win_iocp_socket_service_base::start_connect_op() and boost::asio::detail::win_iocp_socket_connect_op::do_complete() with trace between every line so that we can identify which call is freezing. Thanks. |
This is the best I could do. I cannot add the urls as I mentioned there: https://svn.boost.org/trac/boost/ticket/10674
My official release(based on 1.56) ships with debug symbols in the a .pdb file. Will this be enough if a user runs WinDbg? If yes, please provide instructions on what a user has to do to capture a callstack. I am totally a noob on working with debuggers. |
I think you can right click the process in Task Manager and choose Create Dump File. http://support.microsoft.com/kb/931673 Getting a dump while it's frozen, plus the .exe/.dlls and .pdb, might be enough. |
@junpet Can you install the official v3.1.10 release? (not the one posted here). If yes, follow the instructions of chriskohlhoff above, and post the dumped file somewhere or send it to my email: sledgehammer999 (at) qbittorrent (dot) org. |
@sledgehammer999 I sent you a mail with .dmp, .exe and .pdg files. |
@chriskohlhoff since I can't post urls in the boost bug tracker, here are the files you requested: https://www.dropbox.com/sh/br6q1x5xu08muea/AACMMcEYJaJy4hOIcuPxdH_Ka?dl=0 |
You cannot wait to close any problematic case? If this library is suspicious for god sake put in the official setup the 1.55 booster version. With all my apology! Sorry for bothering you! Best Regards! From: sledgehammer999 [mailto:notifications@github.com] — |
@anyN read again what I have written in my comments and you'll understand. |
O.K. Best Regards! From: sledgehammer999 [mailto:notifications@github.com] @anyN https://github.com/Anyn read again what I have written in my comments and you'll understand. — |
we just went through 2 weeks of hell until we found this thread, we had the very same issue. |
@gubatron were you also using boost 1.56? |
@gubatron if you are also able to capture a debug .dmp (as described above) at the time when the UI hangs it would be helpful. Unfortunately the one I have now does not by itself provide sufficient information to isolate the problem. |
we had built libtorrent using boost 1.56 and 1.57 from source, it wasn't until we turned off every CPU consuming routine, every disk IO consuming routine that we could narrow down the issue to libtorrent's networking IO being the culprit. Then a google with the magic combination of keywords lead us to this conversation, we went back to building with libtorrent using boost 1.55, voilá problem gone. Lost two weeks trying to find this, and probably a load of users. |
…st IO in Windows. Very similar to a qBittorrent issue and fixed using boost 1.55. Updated Windows binary. Relevant links: qbittorrent/qBittorrent#2003 boostorg/asio@0484963 https://svn.boost.org/trac/boost/ticket/10674
Still having problem on 3.2.3. |
@Lilfut |
@ everyone who had freezing problems due to boost 1.56. Can you help me test new versions? |
@sledgehammer999 Sorry for late answer, here my test. The first two .exe-s causes freezin, the third one (1.59-NO_CONNECTEX) works well. I'll continue using this. I'll report if something goes wrong. Thank you! I ♥ qBittorrent! |
Thanks for report. I'll change to more recent boost version in next release. |
Hi, did you use 1.59-NO_CONNECTEX Boost version on the official Windows v3.3.1 installer? I have been getting this issue (or something similar) on Windows 10 x64 for a while with the official release. I downloaded version 3.2.5 above and tried only the 1.59-NO_CONNECTEX version and it has been working great for a few hours now -- whereas if I use the official binary, my entire system begins to stop responding within 5 to 10 minutes, and I am pretty much forced to reboot. Maybe it's an entirely different issue, but all I know is the version in the 1.59-NO_CONNECTEX folder works great so far, so I post it here. Please let me know if there is any other information that would be useful, and thank you! :) Edit: nevermind, happened after a few more hours. Edit2: if I disable DHT, the issue never happens again. Been over a week uptime now. |
After updating to 3.1.10 I noticed that when I'm downloading a torrent, the UI frequently hangs when I click on it(shows not responding on the titlebar). The client still works and doesn't crash, it just takes a while before it "gets" the click.
This doesn't seem to happen when I'm not downloading something.
edit: Win7 x64, SP1
The text was updated successfully, but these errors were encountered: