Tooltip rendering has slowed down considerably with new chrome version (v38)

[sherin]

Hi,

Our line charts that don't use interactive-guideline has slowed down considerably with the latest chrome upgrade (version 38). The tooltips take a good 15 seconds and over before they show up. I can repro this problem on the nvd3 examples page too - http://nvd3.org/examples/lineWithFocus.html. We have tried chrome 37 and chrome 38 on Mac 10.9 and the graphs work fine with chrome version 37 but very slow with 38.

Is anyone else having this problem?

Thanks!
Sherin

[driftingaway]

Yes. Pretty dramatic slowdown of most of nvd3. Works fine in anything but chrome 38. Sufficiently large pages (multiple nvd3 figures) is sufficient to actually crash the page.

[renathy]

Same here. Chrome crashes.

[driftingaway]

Chrome bug on this issue: https://code.google.com/p/chromium/issues/detail?id=423749

[david0178418]

Same here. I was trying to figure out if I should file it to the Chromium team or here. Great to see both taken care of already.

[venu-gande]

Same here. We use nvd3 charts with considerably many data points (around 1500 ) . With chrome 38 our charts are not even responding.

[krisrogers]

Experience the same problem in a web application deployed via Chromium Portable. Chrome 37 works fine, then 38 is massively slower.

[krisrogers]

Also, tested with 39.0.2171.42 beta-m and the problem is still there 👎

[henrilouis]

Same stuff: the scatterchart just freezes Chrome when adding more than 10 datapoints.

[davehaddon]

I have just noticed this problem on a Line chart with around 1400 points. If I enable 'interactive', the whole thing freezes for about 70-90 seconds.
In playing around with different settings, I found that chart.useInteractiveGuideline(true) is fine with no noticeable delays at all.

[liquidpele]

Hi all, I didn't see any issues with my fork.... it has a lot of fixes that aren't in the master of this project (which has essentially stopped development), if you can reproduce on the development branch of my fork then I'll try to see what's up...

https://github.com/liquidpele/nvd3/tree/development

[liquidpele]

Okay, I actually fixed this in my fork's development branch. It had to do with how nvd3 was using the voronoi points in chrome. Cheers.

[liquidpele]

Should be fixed in latest novus version.

[venu-gande]

I had the same problem. I just stopped using voronoi for tooltip.. Everything works fine now ..

[liquidpele]

Should be fixed in latest nvd3 version 1.7.x+, thanks!