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

Network Graph throwing "Maximum call stack size exceeded" error #9803

Closed
trentmwillis opened this issue Jan 4, 2019 · 3 comments

Comments

@trentmwillis
Copy link
Contributor

commented Jan 4, 2019

Expected behaviour

A networkgraph series with the following data should render without error:

["1", "2"],
["2", "1"],
["3", "1"]

Actual behaviour

An error is thrown with the following stack trace:

Uncaught RangeError: Maximum call stack size exceeded
    at Array.forEach (<anonymous>)
    at a (networkgraph.src.js:312)
    at networkgraph.src.js:314
    at Array.forEach (<anonymous>)
    at a (networkgraph.src.js:312)
    at networkgraph.src.js:314
    at Array.forEach (<anonymous>)
    at a (networkgraph.src.js:312)
    at networkgraph.src.js:314
    at Array.forEach (<anonymous>)

Live demo with steps to reproduce

  1. Visit the demo at https://jsfiddle.net/wz4n37c8/
  2. Open the browser console and notice the error

Product version: 7.0.1

Affected browser: Chrome

trentmwillis added a commit to trentmwillis/highcharts that referenced this issue Jan 4, 2019
trentmwillis added a commit to trentmwillis/highcharts that referenced this issue Jan 4, 2019

@ghost ghost assigned pawelfus Jan 7, 2019

@ghost ghost added the Status: Review label Jan 7, 2019

@ghost ghost removed the Status: Review label Jan 7, 2019

@trentmwillis

This comment has been minimized.

Copy link
Contributor Author

commented Jan 7, 2019

When could we expect a release with this bug fix? Just want to set expectations for users 🙂

@pawelfus

This comment has been minimized.

Copy link
Contributor

commented Jan 7, 2019

We don't have ETA for the next release. In general releases are done every month or two, so I would expect beginning of the February.

Heads up:
It's a bug in default options series.layoutAlgorithm.initialPositions, you can resolve the issue at this moment: https://jsfiddle.net/BlackLabel/kpnsgLoa/ (custom function) or use semi-random positions: https://jsfiddle.net/BlackLabel/kpnsgLoa/2/ (second build-in function).

@trentmwillis

This comment has been minimized.

Copy link
Contributor Author

commented Jan 7, 2019

Okay, sounds good. Thanks!

@pawelfus pawelfus added the Type: Bug label Mar 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.