{"action":"created","issue":{"url":"https://api.github.com/repos/powerline/powerline/issues/1758","repository_url":"https://api.github.com/repos/powerline/powerline","labels_url":"https://api.github.com/repos/powerline/powerline/issues/1758/labels{/name}","comments_url":"https://api.github.com/repos/powerline/powerline/issues/1758/comments","events_url":"https://api.github.com/repos/powerline/powerline/issues/1758/events","html_url":"https://github.com/powerline/powerline/issues/1758","id":224765791,"number":1758,"title":"Powerline affects tmux 2.4 CPU usage?","user":{"login":"maotora","id":5174884,"avatar_url":"https://avatars1.githubusercontent.com/u/5174884?v=3","gravatar_id":"","url":"https://api.github.com/users/maotora","html_url":"https://github.com/maotora","followers_url":"https://api.github.com/users/maotora/followers","following_url":"https://api.github.com/users/maotora/following{/other_user}","gists_url":"https://api.github.com/users/maotora/gists{/gist_id}","starred_url":"https://api.github.com/users/maotora/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maotora/subscriptions","organizations_url":"https://api.github.com/users/maotora/orgs","repos_url":"https://api.github.com/users/maotora/repos","events_url":"https://api.github.com/users/maotora/events{/privacy}","received_events_url":"https://api.github.com/users/maotora/received_events","type":"User","site_admin":false},"labels":[{"id":75570929,"url":"https://api.github.com/repos/powerline/powerline/labels/c:b:tmux","name":"c:b:tmux","color":"5379e7","default":false},{"id":6886229,"url":"https://api.github.com/repos/powerline/powerline/labels/t:bug","name":"t:bug","color":"FF0000","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2017-04-27T12:21:40Z","updated_at":"2017-04-30T17:14:01Z","closed_at":null,"body":"Hello,\r\n\r\nI recently updated to `tmux V 2.4` and soon started to notice the huge increase in tmux [CPU usage](https://github.com/tmux/tmux/issues/889). \r\n\r\nToday I set up to get in this and found out when I commented my tmux powerline sourcing line \r\n`\r\nsource \"/usr/lib/python3.6/site-packages/powerline/bindings/tmux/powerline.conf\"\r\n`\r\ntmux works normally (without eating CPU).\r\n\r\nIt's probably not helpful but I tried changing my powerline/theme configurations to \r\n`$ touch empty.json` and reflected that in `~/.config/powerline/config.json` lost theme as expected but tmux ran smoothly.\r\n\r\n\r\nIf I remove every line and keep just the barebones which don't display anything however CPU goes up again.\r\n\r\nLike this :- \r\n\r\n```\r\n{\r\n\t\"segments\": {\r\n\t\t\"right\": [\r\n        ]\r\n\t}\r\n}\r\n```\r\nPlease help."},"comment":{"url":"https://api.github.com/repos/powerline/powerline/issues/comments/298244389","html_url":"https://github.com/powerline/powerline/issues/1758#issuecomment-298244389","issue_url":"https://api.github.com/repos/powerline/powerline/issues/1758","id":298244389,"user":{"login":"ZyX-I","id":322097,"avatar_url":"https://avatars0.githubusercontent.com/u/322097?v=3","gravatar_id":"","url":"https://api.github.com/users/ZyX-I","html_url":"https://github.com/ZyX-I","followers_url":"https://api.github.com/users/ZyX-I/followers","following_url":"https://api.github.com/users/ZyX-I/following{/other_user}","gists_url":"https://api.github.com/users/ZyX-I/gists{/gist_id}","starred_url":"https://api.github.com/users/ZyX-I/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ZyX-I/subscriptions","organizations_url":"https://api.github.com/users/ZyX-I/orgs","repos_url":"https://api.github.com/users/ZyX-I/repos","events_url":"https://api.github.com/users/ZyX-I/events{/privacy}","received_events_url":"https://api.github.com/users/ZyX-I/received_events","type":"User","site_admin":false},"created_at":"2017-04-30T17:14:01Z","updated_at":"2017-04-30T17:14:01Z","body":"@pjcj This does not look like a powerline bug, I cannot imagine a good reason for additional tmux call (which would be fork+exec+connecting and writing to the socket, processing on the server, then reading back and passing that via stdout) produce less CPU usage. Though out of all actions only reading and processing are performed on the server (and contribute to visible tmux CPU usage), but everything else should contribute to the total CPU usage."}}
{"actor":{"display_login":"ZyX-I"}}