{"action":"created","issue":{"url":"https://api.github.com/repos/VSCodeVim/Vim/issues/2124","repository_url":"https://api.github.com/repos/VSCodeVim/Vim","labels_url":"https://api.github.com/repos/VSCodeVim/Vim/issues/2124/labels{/name}","comments_url":"https://api.github.com/repos/VSCodeVim/Vim/issues/2124/comments","events_url":"https://api.github.com/repos/VSCodeVim/Vim/issues/2124/events","html_url":"https://github.com/VSCodeVim/Vim/issues/2124","id":272433505,"number":2124,"title":"CPU ran into 200%+ in VSCode 1.18.0","user":{"login":"gonghao","id":343991,"avatar_url":"https://avatars0.githubusercontent.com/u/343991?v=4","gravatar_id":"","url":"https://api.github.com/users/gonghao","html_url":"https://github.com/gonghao","followers_url":"https://api.github.com/users/gonghao/followers","following_url":"https://api.github.com/users/gonghao/following{/other_user}","gists_url":"https://api.github.com/users/gonghao/gists{/gist_id}","starred_url":"https://api.github.com/users/gonghao/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gonghao/subscriptions","organizations_url":"https://api.github.com/users/gonghao/orgs","repos_url":"https://api.github.com/users/gonghao/repos","events_url":"https://api.github.com/users/gonghao/events{/privacy}","received_events_url":"https://api.github.com/users/gonghao/received_events","type":"User","site_admin":false},"labels":[{"id":609278371,"url":"https://api.github.com/repos/VSCodeVim/Vim/labels/area/performance","name":"area/performance","color":"c2e0c6","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2017-11-09T04:00:54Z","updated_at":"2018-03-08T20:37:30Z","closed_at":null,"author_association":"NONE","body":"<!--\r\nFor questions, ask us on [Slack](https://vscodevim-slackin.azurewebsites.net/) 👫. \r\nDONT CHANGE ANYTHING UNTIL THE -----. Thanks!\r\n-->\r\n\r\n* Click *thumbs-up* 👍 on this issue if you want it!\r\n* Click *confused* 😕 on this issue if not having it makes VSCodeVim unusable. \r\n\r\nThe VSCodeVim team prioritizes issues based on reaction count. \r\n\r\n--------\r\n\r\n**Is this a BUG REPORT or FEATURE REQUEST?** (choose one): **BUG REPORT**\r\n\r\n<!--\r\nIf this is a BUG REPORT, please:\r\n  - Fill in as much of the template below as you can.  If you leave out\r\n    information, we can't help you as well.\r\n\r\nIf this is a FEATURE REQUEST, please:\r\n  - Describe *in detail* the feature/behavior/change you'd like to see.\r\n\r\nIf we can't reproduce a bug or think a feature already exists, we\r\nmight close your issue.  If we're wrong, PLEASE feel free to reopen it and\r\nexplain why.\r\n-->\r\n\r\n**Environment**:\r\n\r\n<!--\r\nPlease ensure you are on the latest VSCode + VSCodeVim\r\n-->\r\n\r\n- **VSCode Version**: 1.18.0\r\n- **VsCodeVim Version**: 0.10.2\r\n- **OS**: macOS 10.13.2 Beta (17C67b)\r\n\r\n**What happened**:\r\n\r\nWhen I upgrade to VSCode 1.18.0 the CPU ran into extreme high, I found it caused by two `Code Helper.app` processes. Then I just disabled all extensions, everything is OK. It is clear that this issues is caused by extensions conflicts with VSCode, so I re-enabled each extension to figure out which one caused this situation. Finally I found it is VSCodeVim, I just re-enabled every other extensions everything is OK, but after re-enable VSCodeVim, the CPU went high.\r\n\r\nSo I don't know do you guys have the same issue?\r\n\r\n<!--\r\nExact keys you pressed.\r\n-->\r\n\r\n**What did you expect to happen**: \r\n\r\nNormal CPU usage.\r\n\r\n**How to reproduce it**:\r\n\r\n- Install VSCode 1.18.0\r\n- Install VSCodeVim and enabled it\r\n"},"comment":{"url":"https://api.github.com/repos/VSCodeVim/Vim/issues/comments/371616425","html_url":"https://github.com/VSCodeVim/Vim/issues/2124#issuecomment-371616425","issue_url":"https://api.github.com/repos/VSCodeVim/Vim/issues/2124","id":371616425,"user":{"login":"Chillee","id":6355099,"avatar_url":"https://avatars1.githubusercontent.com/u/6355099?v=4","gravatar_id":"","url":"https://api.github.com/users/Chillee","html_url":"https://github.com/Chillee","followers_url":"https://api.github.com/users/Chillee/followers","following_url":"https://api.github.com/users/Chillee/following{/other_user}","gists_url":"https://api.github.com/users/Chillee/gists{/gist_id}","starred_url":"https://api.github.com/users/Chillee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Chillee/subscriptions","organizations_url":"https://api.github.com/users/Chillee/orgs","repos_url":"https://api.github.com/users/Chillee/repos","events_url":"https://api.github.com/users/Chillee/events{/privacy}","received_events_url":"https://api.github.com/users/Chillee/received_events","type":"User","site_admin":false},"created_at":"2018-03-08T20:37:30Z","updated_at":"2018-03-08T20:37:30Z","author_association":"MEMBER","body":"Does anybody still get this issue on recent versions of VSCodeVim?"}}
{"actor":{"display_login":"Chillee"}}