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

Console errors when zoomed in and using series.setData with redraw set to false #8795

Closed
matdion opened this issue Aug 16, 2018 · 5 comments
Closed

Comments

@matdion
Copy link

@matdion matdion commented Aug 16, 2018

Expected behaviour

Zooming in on a live updated chart should not trigger console errors on chart hover.
I need to throttle redraws on a chart to prevent it being redrawn on ever serie's setData.
Is this use case supposed to work or there another way to achieve throttling

Actual behaviour

When using a deferred chart.redraw instead of a direct redraw on serie.setData hovering the chart when zoomed in will trigger hundreds of console errors.

FF 61.0.2 Error:
11:35:06.165 TypeError: h.series is null[Learn More] 18 highcharts.js:186:59 findNearestKDPoint/< https://code.highcharts.com/6.0.0/highcharts.js:186:59 forEach self-hosted:268:13 a.each https://code.highcharts.com/6.0.0/highcharts.js:28:236 findNearestKDPoint https://code.highcharts.com/6.0.0/highcharts.js:185:381 getHoverData https://code.highcharts.com/6.0.0/highcharts.js:187:240 runPointActions https://code.highcharts.com/6.0.0/highcharts.js:188:272 onContainerMouseMove https://code.highcharts.com/6.0.0/highcharts.js:197:204 setDOMEvents/c.onmousemove https://code.highcharts.com/6.0.0/highcharts.js:199:123

Chrome 68.0.3440.106 Error (IE11 has the same):
highcharts.js:186 Uncaught TypeError: Cannot read property 'group' of null at highcharts.js:186 at Array.forEach (<anonymous>) at a.each (highcharts.js:28) at a.Pointer.findNearestKDPoint (highcharts.js:185) at a.Pointer.getHoverData (highcharts.js:187) at a.Pointer.runPointActions (highcharts.js:188) at a.Pointer.onContainerMouseMove (highcharts.js:197) at HTMLDivElement.c.onmousemove (highcharts.js:199) (anonymous) @ highcharts.js:186 a.each @ highcharts.js:28 findNearestKDPoint @ highcharts.js:185 getHoverData @ highcharts.js:187 runPointActions @ highcharts.js:188 onContainerMouseMove @ highcharts.js:197 c.onmousemove @ highcharts.js:199

Live demo with steps to reproduce

Deferred redraw causes console error https://jsfiddle.net/ma_di/Laxsvgbw

  1. To reproduce zoom in close and hover the series.

Direct redraw has no error but kills the cpu usage https://jsfiddle.net/ma_di/81mhcp07/

Product version

Highcharts 6.X.X
Highcharts 6.1.X will also cause #8355

Affected browser(s)

Chrome
Firefox
IE11

@sebastianbochan
Copy link
Contributor

@sebastianbochan sebastianbochan commented Aug 17, 2018

Hi @matdion,
Thank you for reporting. Its a bug.

v6.0.0
zrzut ekranu 2018-08-17 o 10 06 00

v6.1.1
zrzut ekranu 2018-08-17 o 10 05 44

The problem also appears without boost module.
Demo:

zrzut ekranu 2018-08-17 o 10 07 38

The different time in setInterval does not have influence on error.

@KacperMadej
Copy link
Contributor

@KacperMadej KacperMadej commented Jul 11, 2019

There's been a revert that accidentally (so it seems) canceled this fix.
92dbf4a

The problem is still visible in version 7.1.2, so I will reopen the issue.
It looks like all this was done and lost between versions 6.1.1 and 6.1.2, so we don't have a release with the fix.

As a workaround you could try using the same solution applied to current code, but please note that this solution was not fully tested yet. Demo: https://jsfiddle.net/BlackLabel/wj4et7c9/1/

@sacrarat
Copy link

@sacrarat sacrarat commented Apr 13, 2020

Any update on getting this fix incorporated in a release?

@sebastianbochan
Copy link
Contributor

@sebastianbochan sebastianbochan commented Apr 14, 2020

Hi @sacrarat,
At this moment we do not have any ETA for fixing this bug.

@sacrarat
Copy link

@sacrarat sacrarat commented Apr 14, 2020

Thanks for the quick response @sebastianbochan . For the time being I've used the suggested workaround and it seems to work.

khlieng added a commit that referenced this issue Dec 11, 2020
@khlieng khlieng self-assigned this Dec 11, 2020
@circleci-mu circleci-mu added this to To do in Development-Flow via automation Dec 11, 2020
@circleci-mu circleci-mu moved this from To do to In progress in Development-Flow Dec 11, 2020
@khlieng khlieng self-assigned this Dec 11, 2020
Development-Flow automation moved this from In progress to Done Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

6 participants