New issue
Advanced search Search tips

Issue 847862 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Uncaught (in promise) Maximum call stack size exceeded

Project Member Reported by nherring@google.com, May 30 2018

Issue description

Chrome Version: 66.0.3359.181
OS: MacOS 10.13.4 (17E202), Debian rodete

What steps will reproduce the problem?
(1) Browse to https://bl.ocks.org/magjac/704d486e783cf1d4a1e69ed4d33a1797

What is the expected result?
It takes a while (<20m), but it should render a diagram which you have to click & mousewheel scroll to zoom out to see.

What happens instead?
Linux presents a bunch of "unresponsive" notices, which you click "Wait" on. Eventually both OS chromes render a page without the diagram, and the inspector yields a JS error: "Uncaught (in promise) Maximum call stack size exceeded" which is happening under https://gist.github.com/magjac/704d486e783cf1d4a1e69ed4d33a1797#file-index-html-L25

Firefox can render this, though you have to increase dom.max_script_run_time.

Safari ended up reloading the page due to non-responsiveness, but eventually rendered it.

Not having a stack trace makes it difficult to figure out what is happening. I do not appear to be able to programmatically increase the stack limit to even find what the high-water mark is.

 

Sign in to add a comment