Saturday, 15 February 2014

javascript - HighCharts/HighStock memory leak with addPoints() in Chrome only -



javascript - HighCharts/HighStock memory leak with addPoints() in Chrome only -

the "dynamically updated data" demo on highstock website seems leak memory in current version of google chrome (24.0). i've tried on mac os x 10.8.2 , windows 7 (64-bit). tried safari 6.0.2 on os x, , both ie9 , firefox 18 on windows 7. leaking seems happen in chrome, , happens.

given prominent demo, have expected work well. given plenty time, crashes in chrome, giving "aw, snap" error page. can take long time in demo written, if click jsfiddle link , alter setinterval() phone call 100 ms instead of 1000 ms, leak obvious. real application multiple series , decent amount of info can crash chrome in few minutes.

note while info beingness added continuously, "shift" parameter in addpoints() true, meaning old info beingness discarded quickly. memory usage should constant--and on browsers other chrome, is.

i'm not sure how tell if chrome bug or highcharts one. , haven't found useful workaround. conclusive reply either aspect much appreciated.

inspired mark's comment, decided seek different versions of various things. first tried bleeding-edge versions of jquery , highstock. chrome 24 (stable) still leaked. tried chrome 23 since worked mark on fedora, still leaked on mac os.

then tried chrome canary build, 26.0. worked, no leaks! exhibited classic garbage collection pattern of building few dozen megabytes excess memory usage, falling downwards "normal", every few seconds. that's news. bad news chrome beta, 25.0, still leaks. if other users of highcharts experience issue in next couple months, they'll need either utilize "unstable" version of chrome, or different brand of browser.

javascript google-chrome memory-leaks highcharts highstock

No comments:

Post a Comment