Release: 2.0.4.29 (canary) 2019-09-17

[kenkendk]

@ts678

There are multiple report of the CPU issue from multiple people on multiple OSs. I hope someone with the right tools (perhaps a profiler?)

I have a suspicion that it is the usage reporter:

Issues to address to get out of beta

Not sure why this is happening again, but it smells like the usage reporter going bonkers. It could be related to the updated CoCoL library, which may have tinkered just a bit with how the timeout exceptions are thrown so they are no longer correctly detected. That sounds like the usage reporter. It waits a little after starting before running the report submission code.