{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/3573","repository_url":"https://api.github.com/repos/Microsoft/visualfsharp","labels_url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/3573/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/3573/comments","events_url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/3573/events","html_url":"https://github.com/Microsoft/visualfsharp/issues/3573","id":257446643,"number":3573,"title":"Continuous high CPU, Team Explorer flashing when opening FSharp solution from Github","user":{"login":"abelbraaksma","id":16015770,"avatar_url":"https://avatars1.githubusercontent.com/u/16015770?v=4","gravatar_id":"","url":"https://api.github.com/users/abelbraaksma","html_url":"https://github.com/abelbraaksma","followers_url":"https://api.github.com/users/abelbraaksma/followers","following_url":"https://api.github.com/users/abelbraaksma/following{/other_user}","gists_url":"https://api.github.com/users/abelbraaksma/gists{/gist_id}","starred_url":"https://api.github.com/users/abelbraaksma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abelbraaksma/subscriptions","organizations_url":"https://api.github.com/users/abelbraaksma/orgs","repos_url":"https://api.github.com/users/abelbraaksma/repos","events_url":"https://api.github.com/users/abelbraaksma/events{/privacy}","received_events_url":"https://api.github.com/users/abelbraaksma/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2017-09-13T16:40:02Z","updated_at":"2017-09-22T17:19:35Z","closed_at":null,"author_association":"NONE","body":"VS2017 15.4.0 P2 + latest nightlies FSharp.\r\n\r\nWhen opening a new copy through Git (Team Explorer > Clone) then opening FSharp.sln (which will partially fail, needs to be build from cmd line first), the Team Explorer will start flashing and VS2017 and MSBuild go nuts:\r\n\r\n**Flashing Team Explorer**\r\n\r\n![flashingteamexplorer_fsharpsln](https://user-images.githubusercontent.com/16015770/30389070-270a5b80-98b2-11e7-863c-a3933c20e659.gif)\r\n\r\n** High CPU**\r\n\r\n![image](https://user-images.githubusercontent.com/16015770/30389150-5dc8fe2e-98b2-11e7-8a8a-5bd0148fed82.png)\r\n\r\n### Repro steps\r\n\r\n1. Open Team Explorer, select Git Clone, enter VisualFSharp Git repo\r\n2. Open FSharp.sln\r\n3. Go back to Team Explorer\r\n4. Behavior as shown\r\n\r\n### Expected behavior\r\n\r\nNo flashing expected. The high CPU is perhaps expected, not sure.\r\n\r\n### Actual behavior\r\n\r\nFlashing as in the video. High CPU for about 1-2 min (I didn't keep track). Then the CPU stopped and the flashing stopped.\r\n\r\n### Known workarounds\r\n\r\nWait it out.\r\n\r\n### Related information \r\n\r\nVS 2017 v15.4.0 Preview 2 on Windows 7, all updates installed.\r\n\r\nNot sure this is \"normal\" or \"expected\" behavior. Not sure this is related to the F# repo, or a VS2017 bug. And I haven't tested this in older VS's or RTM's."},"comment":{"url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/comments/331507943","html_url":"https://github.com/Microsoft/visualfsharp/issues/3573#issuecomment-331507943","issue_url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/3573","id":331507943,"user":{"login":"abelbraaksma","id":16015770,"avatar_url":"https://avatars1.githubusercontent.com/u/16015770?v=4","gravatar_id":"","url":"https://api.github.com/users/abelbraaksma","html_url":"https://github.com/abelbraaksma","followers_url":"https://api.github.com/users/abelbraaksma/followers","following_url":"https://api.github.com/users/abelbraaksma/following{/other_user}","gists_url":"https://api.github.com/users/abelbraaksma/gists{/gist_id}","starred_url":"https://api.github.com/users/abelbraaksma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abelbraaksma/subscriptions","organizations_url":"https://api.github.com/users/abelbraaksma/orgs","repos_url":"https://api.github.com/users/abelbraaksma/repos","events_url":"https://api.github.com/users/abelbraaksma/events{/privacy}","received_events_url":"https://api.github.com/users/abelbraaksma/received_events","type":"User","site_admin":false},"created_at":"2017-09-22T17:19:35Z","updated_at":"2017-09-22T17:19:35Z","author_association":"NONE","body":">  But I figured, this is an MS prj by MS people (and a lot of volunteers), so let's stick to the toolchain they offer. It somehow seemed to make sense.\r\n\r\n@vasily-kirichenko, rereading my own comment it looks rather derisive, it wasn't meant that way, my apologies. I'm just starting out getting test coverage working and I figured, let's stick to the defaults given by the instructions in DEVGUIDE.md, before getting more adventurous and trying it with other tools. \r\n\r\nCertainly, I didn't mean to suggest this project may only be used with MS tools, on the contrary ;), your input is very valuable to me."}}
{"actor":{"display_login":"abelbraaksma"}}