{"action":"created","issue":{"url":"https://api.github.com/repos/owncloud/client/issues/4915","repository_url":"https://api.github.com/repos/owncloud/client","labels_url":"https://api.github.com/repos/owncloud/client/issues/4915/labels{/name}","comments_url":"https://api.github.com/repos/owncloud/client/issues/4915/comments","events_url":"https://api.github.com/repos/owncloud/client/issues/4915/events","html_url":"https://github.com/owncloud/client/issues/4915","id":157227159,"number":4915,"title":"Abusive CPU Usage","user":{"login":"theonlydoo","id":1903124,"avatar_url":"https://avatars.githubusercontent.com/u/1903124?v=3","gravatar_id":"","url":"https://api.github.com/users/theonlydoo","html_url":"https://github.com/theonlydoo","followers_url":"https://api.github.com/users/theonlydoo/followers","following_url":"https://api.github.com/users/theonlydoo/following{/other_user}","gists_url":"https://api.github.com/users/theonlydoo/gists{/gist_id}","starred_url":"https://api.github.com/users/theonlydoo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/theonlydoo/subscriptions","organizations_url":"https://api.github.com/users/theonlydoo/orgs","repos_url":"https://api.github.com/users/theonlydoo/repos","events_url":"https://api.github.com/users/theonlydoo/events{/privacy}","received_events_url":"https://api.github.com/users/theonlydoo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-05-27T15:05:44Z","updated_at":"2016-05-28T17:00:18Z","closed_at":null,"body":"### Expected behaviour\r\nNot using 100% CPU from 2 cores all the time while there is no sync\r\n\r\n### Actual behaviour\r\nThe exact opposite\r\n\r\n### Steps to reproduce\r\n1. Fedora 23\r\n2.  Owncloud client latest\r\n3.  htop\r\n\r\n### Server configuration\r\nOperating system:\r\nFedora23\r\nWeb server: \r\nNginx\r\nDatabase:\r\nMariadb\r\nPHP version:\r\n5.6\r\nownCloud version:\r\nLatest\r\nStorage backend:\r\nfilesystem\r\n### Client configuration\r\nClient version:\r\n```\r\nlibowncloudsync0-2.2.0-9.1.x86_64\r\nowncloud-client-2.2.0-9.1.x86_64\r\nowncloud-client-l10n-2.2.0-9.1.x86_64\r\n```\r\nOperating system:\r\nFedora23\r\nOS language:\r\nFr\r\nInstallation path of client:\r\n/usr/bin/owncloud\r\n![selection_294](https://cloud.githubusercontent.com/assets/1903124/15611996/3d3f4870-242d-11e6-931c-b9691a4f6fab.png)\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/owncloud/client/issues/comments/222318536","html_url":"https://github.com/owncloud/client/issues/4915#issuecomment-222318536","issue_url":"https://api.github.com/repos/owncloud/client/issues/4915","id":222318536,"user":{"login":"prairietree","id":19625784,"avatar_url":"https://avatars.githubusercontent.com/u/19625784?v=3","gravatar_id":"","url":"https://api.github.com/users/prairietree","html_url":"https://github.com/prairietree","followers_url":"https://api.github.com/users/prairietree/followers","following_url":"https://api.github.com/users/prairietree/following{/other_user}","gists_url":"https://api.github.com/users/prairietree/gists{/gist_id}","starred_url":"https://api.github.com/users/prairietree/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prairietree/subscriptions","organizations_url":"https://api.github.com/users/prairietree/orgs","repos_url":"https://api.github.com/users/prairietree/repos","events_url":"https://api.github.com/users/prairietree/events{/privacy}","received_events_url":"https://api.github.com/users/prairietree/received_events","type":"User","site_admin":false},"created_at":"2016-05-28T17:00:18Z","updated_at":"2016-05-28T17:00:18Z","body":"I do not want to abuse this comment, but I typed up all this information before I found this similar issue open. In addition to what is mentioned here I am also having excessive ram usage after a while of running ownCloud client.\r\n\r\n## Expected behaviour\r\nOwnCloud Linux client maintains it cpu and ram usage so as to keep the system responsive.\r\n\r\n### Actual behaviour\r\nOn a large new sync 40 GB of mostly pictures cpu usage stayed at 90+%, and ram usage will eventually start climbing tell the system is unresponsive.\r\n\r\n### Steps to reproduce\r\n1. Install the latest linux owncloud client on Kubuntu 16.04 or 14.04.\r\n2. Try to sync 40 or so GB of mostly pictures.\r\n3. \r\n\r\n### Server configuration\r\nOperating system: Ubuntu server 14.04\r\n\r\nWeb server: Apache\r\n\r\nDatabase: MySql\r\n\r\nPHP version: \r\n\r\nownCloud version: 9.0.1\r\n\r\nStorage backend:\r\n\r\n### Client configuration\r\nClient version: \"Version 2.2.0%nil (build 1605).\"\r\n\r\nOperating system: Linux Kubuntu 16.04\r\n\r\nOS language: English\r\n\r\nInstallation path of client: /usr/bin/owncloud\r\n\r\n### Logs\r\n\r\n1. Output of `owncloud --logwindow` or `owncloud --logfile log.txt`\r\n\r\n```I will try to rerun it latter with logging enabled. I did not know I needed to enable it.```\r\n\r\n2. Web server error log:\r\n\r\n3. ownCloud log (data/owncloud.log):\r\n\r\n### The story\r\n\r\nI am having trouble with high cpu usage when running own cloud client on Kubuntu. I was having the same trouble with Kubuntu 14.04 so I upgraded to Kubuntu 16.04 last week, and installed the latest ownCloud client. After I added two syncs, one of less then 30 MB and one of about 40 GB. I noticed right away the system became very unresponsive. I looked at the processes cpu usage and did not see anything very high so I tried to do some other stuff my system and it locked up and I had to force a restart. A few minutes later the system locked up again but I had a terminal open and was able to shut it down from there. This morning I started the computer up again and let it set for 10 minutes or so and then looked at it. The ownCloud process was only using 8-12 percent of the cpu and nothing else in the system monitor was using much. But when I looked at the System Load tab three cpu threads where stuck at 100 percent and the fourth was jumping between 60 and a 100 percent. So I am not sure why the discrepancy. During that time the system was really slow. It took 3 to 5 minutes to load fire fox. There was also lots of disk activity. I paused both syncs in ownCloud but that did not help, so I stopped the ownCloud process and the cpu usage dropped down to basically zero over the next few seconds.\r\n\r\nAfter that I tried to restart ownCloud client but it would not come up. The icon appeared on the system try and would say in a pop up that syncing was disabled but clicking on it or ownCloud in the start menu would do nothing.\r\n\r\nI then restarted Kubuntu and ownCloud client popped right up on the screen, both syncs were paused. I waited a minute, then started the smaller sync. Most of the cpu's hit 60-80 percent but then went right back down. I waited a few minutes and then started the large sync. It quickly jumped up to one cpu running about a 100 percent (not always the same one), but the others were low. After a minute or so two cpu's hit 100% and basically stayed there. In about an about another minute we had three cpu's at 100%. It varied a little bit after that. Some times they would all be 100% and other times only one would be 100% and the rest would be less. But for the most part they stayed maxed out. The ownCloud process itself seemed to only take about 15% most of the time according to the process monitor. The system stayed responsive for a few minutes more. At some point all network traffic dropped off, but the cpu usage stayed maxed out. The outbound network traffic eventually came back but at a fairly slow rate.\r\n\r\nAfter about ten minutes of this the ram usage suddenly started climbing so I switch to the process tab and it was the ownCloud process that was using most of it. The system has four GB of ram and had been running just under one including ownCloud client. By the time ownCloud client hit three GB the system was mostly unresponsive. It made it up to 3,39x,xxx KB before even the screen would not refresh. I could not get to another console, so I had to hold the power button to force it down. When it restarted I paused the large sync. \r\n\r\nThe smaller sync of 30 MB or less seems to be working."}}
{"actor":{"display_login":"prairietree"}}