-
Notifications
You must be signed in to change notification settings - Fork 30
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
Pausing syncthing using the menu, causes almost 200% cpu usage. #182
Comments
sweet! thanks! 👍 And yeah, technically I dont get 200%, but I do get blocking on the main thread for a while. Either way, this will be fixed as part of #176 (comment) - the process handling isnt in a good state and I need to rewrite it completely and move it out of the Connection Handling. It doesn't belong there and the only reason it actually is, was because I've been a bit lazy when I started QST. |
Yeah it climbs to near 200 and stays there. |
I can confirm buggy behavior on 0.5.5rc1 CPU climbing up when pause is clicked from r-click menu. In my case I observed it climbing up to about 97% cpu usage on a 4 core machine and staying there. Running OpenBSD -current amd64 |
Ah, bummer. Either way though, this is the next thing I'll be working on. In fact I already started, but it takes a while. |
If you want to help out, mind checking out this PR #184 and see if it's still an issue? |
This has gone to master by now. Any chance you can check this again? Else I might close this. |
Sorry, been so busy! Will give it a go now. |
This was today's master built with:
|
I can confirm reproducing the same issue (100% CPU usage) tested on commit:
|
Seems OpenBSD specific :/ Guess there's no way around for me setting up OpenBSD and getting to the root of this. |
Hi,
Noticed that qsyncthing tray pegs cores when you pause syncthing.
This is version qsyncthingtray-0.5.5rc1 on OpenBSD. Can you repro?
P.S.
qsyncthingtray is an OpenBSD package now, thanks!
http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/net/qsyncthingtray/
The text was updated successfully, but these errors were encountered: