-
Notifications
You must be signed in to change notification settings - Fork 669
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
[Windows] After upgrade to 2.4.0 client hangs #6272
Comments
Hi, Thanks for the report. I will need additional information in order to investigate this issue. Could you maybe send a screenshot that shows what the client is showing when it is frozen. Do you have the logwindow enabled? Could you run the client with Would you be able to produce traces with gdb to see where it hangs? |
i think it should appear in the "current" directory. I don't know where it is. Use |
Windows might not allow to write there, better specify a good full path. |
I changed it to my home dir and now it writes the log. Waiting until it hangs again... |
I think I found the reason: It's just a GUI freeze, logging goes on.
So it needs 15000 seconds to go through this one folder. |
I removed them and now it seems to work. I had some conflicts, but they where mostly cache files of games. |
@mueller-ma Thanks for investigating! We'd really like to know what triggered the gui-freeze, that should not happen! Do you still have the log file that was written while the gui was frozen? Also, one If you have the full logs could you send them to me? mail at ckamm de EDIT: To clarify, that freeze happens when you click on the "Für Details klicken" message? Then, possibly, the issue list view has a performance problem. I'll see what happens with that view when there are 100k of ignored files. |
I can reproduce the slowness in inserting to the issues widget and will fix that. Probably we both speed up the insertion as well as establish a maximum number of items. |
I think the freeze is unrelated to the click on "Für Details klicken". The mentioned ignored files are 1KB to 40 KB large. |
Since sorting was enabled permanenty the list would be resorted with each inserted issue. When inserting thousands of ignored files that would make the whole ui freeze up. Instead, sorting is disabled for inserts now and is reenabled after some time has passed. That way users usually see the sorted view without the lockups. Also, there's now a maximum of 50k issue entries.
Since sorting was enabled permanenty the list would be resorted with each inserted issue. When inserting thousands of ignored files that would make the whole ui freeze up. Instead, sorting is disabled for inserts now and is reenabled after some time has passed. That way users usually see the sorted view without the lockups. Also, there's now a maximum of 50k issue entries.
@wdsupport @mueller-ma Have you tried a daily build https://download.owncloud.com/desktop/daily/ownCloud-2.5.0.66-daily20180205-setup.exe ? Please report back. |
I havent tried, but I dont have any oh testing env and dont want to use unstable builds in my production env. |
finally I use the daily latest version, and it stop hanging up, thanks mate, surely their was something in the version 2.4 that hang the software.. |
@wdsupport hooray :) |
Expected behaviour
Should work like before update
Actual behaviour
Says there are unresolved conflicts and I should click to resolve them. I click and the client doesnt responed anymore. Also windows explorer doesnt responed anymore.
Steps to reproduce
Server configuration
Operating system: Debian 8
Storage: Folder on the local HDD (ext4)
Client configuration
Client version: 2.4.0
Operating system: Windows 7 64bit
OS language: DE
Installation path of client: C:\Program Files (x86)\ownCloud
Logs
Client logfile: Output of
owncloud --logwindow
orowncloud --logfile log.txt
(On Windows using
cmd.exe
, you might need to firstcd
into the ownCloud directory)(See also http://doc.owncloud.org/desktop/2.2/troubleshooting.html#client-logfile )
Doesnt output anything.
Web server error log:
Possible other reasons:
The text was updated successfully, but these errors were encountered: