Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stack size exceeded error when using responsive rules. #7109

Closed
rredondoo opened this issue Aug 29, 2017 · 3 comments
Closed

Stack size exceeded error when using responsive rules. #7109

rredondoo opened this issue Aug 29, 2017 · 3 comments

Comments

@rredondoo
Copy link

Problem

When resizing a chart that has a responsive rule with the tooltip option, the chart throws the error:
Uncaught RangeError: Maximum call stack size exceeded

Comments:

I could only trigger the error by using the tooltip option. I am not sure if setting other options might also throw an error.

Live demo with steps to reproduce

https://jsfiddle.net/rredondo/x8792he0/

Decrease the width of the window containing the chart to make it smaller than maxWidth (set to 600px).
Make it large again.
The error should appear in the console.

Affected browser(s)

Chrome, Firefox

@TorsteinHonsi
Copy link
Collaborator

Thanks for reporting!

Normalized demo (click the button): https://jsfiddle.net/highcharts/x8792he0/6/

Note that it applies only in stock charts, not in vanilla Highcharts.

@TorsteinHonsi
Copy link
Collaborator

After some digging it comes down to this passage:

https://github.com/highcharts/highcharts/blob/v5.0.14/js/parts/Dynamics.js#L444-L450

When we run series.update on a seires that has a navigator series, something goes wrong. Isolated here: https://jsfiddle.net/highcharts/x8792he0/8/

  1. Click the "Series.update" button.
  2. Observe how one navigator series is added on each iteration.

So either we need to eliminate the navigator series from this update call, or we need to make sure it performs correctly even though we call .update on all series.

@TorsteinHonsi
Copy link
Collaborator

Interestingly, the same issue was just reported at #7110.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants