58.0.3023.0 canary and later spend a ton more time in OnBeginFrameDeadline().

Here's the data from UMA Sampling Data - which is data from the wild from canary users on Windows 64:

58.0.3022.0 canary:
https://uma.googleplex.com/callstacks?sid=f386c362a269e00bff9f28fafd0a90ae

58.0.3023.0 canary:
https://uma.googleplex.com/callstacks?sid=895c08aecb65cfd4972129ed9a3eea05

Current canary 59.0.3060.0:
https://uma.googleplex.com/callstacks?sid=b5390f5dda67274e1a46719c2bba1299

Specifically, from the data, we see that OnBeginFrameDeadline took around but went from ~7ms to ~650ms mean time

Seems most of the time is spent in cc::Program::InitializeInternal:
https://uma.googleplex.com/callstacks?sid=5d7f8d15333adef8176b1d77dd3f6ff1

Whereas, previously hardly any time was spent there:
https://uma.googleplex.com/callstacks?sid=fcf4c24052865f11b4846f78d51a434a

Note: This is sampling data from first 30s of startup.

Changelog: https://chromium.googlesource.com/chromium/src/+log/58.0.3022.0..58.0.3023.0?pretty=fuller&n=10000

Assigning to ccameron@ based on a number of GL-related changes they landed in that range. Chris, could you talk a look? Please re-assign if there's a better owner for this.