I've also seen this issue with Ember 2.5 and 2.6-beta.2. I'm running Chrome 52.0.2716.0 dev (64-bit).

Unable to reproduce this on the latest canary(52.0.2730.0), latest beta(51.0.2704.36), reported version(51.0.2704.29). Attached is the screen-cast of the same.

Could anyone review the attached screen-cast and confirm if anything missed here or if issue is still seen on the latest Beta?

Deleted: 609970.mp4 1.4 MB

609970.mp4 1.4 MB Download

The specific reproduction from above seems to not occur on a fresh window. I cannot reproduce with it any longer.

I can confirm we still see other reproductions on Chrome 50 and 52. The following error is logged via --enable-logging --v=4 --blink-platform-log-channels:

-----------

2016-05-10 17:56:31.348 Google Chrome[90475:962737] NSWindow warning: adding an unknown subview: <FullSizeContentView: 0x7fabb977d570>. Break on NSLog to debug.
2016-05-10 17:56:31.349 Google Chrome[90475:962737] Call stack:
(
    "+callStackSymbols disabled for performance reasons"
)
2016-05-10 17:56:38.497 Google Chrome Helper[90494:963106] Couldn't set selectedTextBackgroundColor from default ()
[90475:1295:0510/175638:ERROR:CONSOLE(0)] "The given range isn't in document.", source: chrome-devtools://devtools/bundled/inspector.html?&remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/@0c319c380220abe3daf0277e40a2d0b22a7c4550/&can_dock=true&dockSide=undocked (0)
[90475:1295:0510/175715:ERROR:CONSOLE(0)] "Uncaught RangeError: Maximum call stack size exceeded", source: chrome-devtools://devtools/bundled/inspector.html?&remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/@0c319c380220abe3daf0277e40a2d0b22a7c4550/&can_dock=true&dockSide=undocked (0)

-----------

I am able to reproduce this somewhat reliably -- I don't have a simple, accessible repro yet. Inspecting the inspector, shows that it hangs after a Max call stack is exceeded. Here is the stack trace:

-----------
  inspector.js:formatted:18552 Uncaught RangeError: Maximum call stack size exceededInspectorBackendClass.Connection._wrapCallbackAndSendMessageObject 
@ inspector.js:formatted:18552 promiseAction 
@ inspector.js:formatted:18761 InspectorBackendClass.AgentPrototype._sendMessageToBackendPromise 
@ inspector.js:formatted:18753 sendMessagePromise 
@ inspector.js:formatted:18695 WebInspector.CPUProfilerModel.stopRecording 
@ inspector.js:formatted:22889 WebInspector.CPUProfileType.stopRecordingProfile 
@ profiler_module.js:533       WebInspector.CPUProfileType.buttonClicked 
@ profiler_module.js:517       WebInspector.ProfilesPanel.toggleRecord 
@ profiler_module.js:82        WebInspector.ProfilesPanel.RecordActionDelegate.handleAction 
@ profiler_module.js:204       handleAction 
@ inspector.js:formatted:9374  Promise.resolve (async)Runtime.Extension.instancePromise 
@ inspector.js:formatted:2949  WebInspector.Action.execute 
@ inspector.js:formatted:9369  WebInspector.Object.dispatchEventToListeners 
@ inspector.js:formatted:4925  WebInspector.ToolbarButton._clicked 
@ inspector.js:formatted:14206
-----------

Thank you for providing more feedback. Adding requester "ajha@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I am also seeing this issue. I'm getting "Uncaught RangeError: Maximum call stack size exceeded" Being thrown by dev tools and it get's stuck on the "Loading Timeline..." screen. Really frustrating when your debug tools have bugs (the worst).