I just found that when starting a profile by clicking the button to start profiles in the inspector results in us reporting profile data for the inspector which seems wholly unhelpful.
* Go to http://nerget.com/ParticleJS/Particles.html
* Open the inspector
* Go to the profile pane
* Click the profile button
* Wait a wee while
* Stop the profile
* Admire the profile of the inspector.
It looks like r34753 is the culprit.
I'll take a look at this tonight.
Although that revision does not look like it could have possibly caused the issue. I think the inspector needs to call startUserInitiatedProfiling() instead of console.profile();
Scratch that calling InspectorController.inspectedWindow().console should contextually be correct in that it should call the console on the inspected window.
> It looks like r34753 is the culprit.
Hum... I can't repro the bug at r34753 but I can repro it at r34754.
That change seems more relevant as touches lines of code that actually run in this case.
Yeah I re-ran my tests and I also think r18754 is the real culprit. Sorry to waste your time. I just need to figure out how this caused the regression.
I'm guessing that somewhere under JSInspectedObjectWrapper::wrapone of these wrappers is holding the wrong ExecState.
Committed revision 35140.