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

boost-canvas crashes when rendering large series (arearange) #10758

Closed
known-as-bmf opened this issue May 17, 2019 · 8 comments
Closed

boost-canvas crashes when rendering large series (arearange) #10758

known-as-bmf opened this issue May 17, 2019 · 8 comments
Labels
Status: Stale This issue hasn't had any activity for a while, and will be auto-closed if no further updates occur. Type: Bug

Comments

@known-as-bmf
Copy link

It seems that rendering area range on very large series with boost (more precisely boost-canvas) imported crashes

Tests ran with:

  • Firefox (66.0.5 (64 bits))
  • Chrome Version 74.0.3729.157 (Build officiel) (64 bits)

Expected behaviour

Chart rendering wether boost or boost-canvas is used

Actual behaviour

Highcharts detects WebGL in Chrome and renders fine,
Highcharts does not detect WebGL in Firefox - error 26 - and crash in boost-canvas.js:196 c.eachAsync is not a function

Live demo with steps to reproduce

Product version

Highcharts latest version (7.1.1)

Affected browser(s)

@sebastianbochan
Copy link
Contributor

Hi @known-as-bmf,
Thank you for reporting about the bug. Currently I did not receive any errors in the Firefox, as a result I was not able to reproduce the issue.

MacOSX 10.12.4.
FF: 66.0.3

Please let me know about your OS / FF version details.

@known-as-bmf
Copy link
Author

Hi,

Thank you for the feedback

I'm using Windows 10 (1809) and the latest FF 66.0.5 (64 bits)

I think the problem is in the boost-canvas module, have you tried disabling WebGL and running the jsfiddle ?

I guess it only happens in FF on my machine because WebGL isn't properly detected

@sebastianbochan
Copy link
Contributor

Hi @known-as-bmf,
I tested in the same environment like yours and still was not able to reproduce the issue. Is it possible to reproduce it in different stable conditions?

@known-as-bmf
Copy link
Author

To reproduce in Chrome:

the following error should appear Uncaught TypeError: c.eachAsync is not a function

@sebastianbochan
Copy link
Contributor

sebastianbochan commented May 21, 2019

Hi @known-as-bmf,
Thank you for details. Now I was able to reproduce the issue.

Windows: 10 (1809)
Chrome: 74.0.3729.157 x64
Disabled webgl.

Internal note
The boost.seriesThreshold = 1 does not solve the issue like I expected when found the other bug: #6842.

FYI @cvasseng

@andnig
Copy link

andnig commented Dec 17, 2019

Hey guys, any news on this issue? I also have troubles with this one as it seems.

@sebastianbochan
Copy link
Contributor

sebastianbochan commented Dec 18, 2019

I have passed the case to our boost developers. He will answer you as soon as possible.

@cvasseng @TorsteinHonsi

@stale
Copy link

stale bot commented Jun 18, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

@stale stale bot added the Status: Stale This issue hasn't had any activity for a while, and will be auto-closed if no further updates occur. label Jun 18, 2021
@stale stale bot closed this as completed Jun 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale This issue hasn't had any activity for a while, and will be auto-closed if no further updates occur. Type: Bug
Projects
None yet
Development

No branches or pull requests

3 participants