OliverBalfour
commented
2 years ago This is partially fixed by leaving the tab open all the time (Chrome on my macbook doesn't process new data when a different tab is open, so it lags for a while when switching back. Running Chrome in the background is fine though)
It's also partially fixed by hiding the text for the vertical valve fire timing indicators at high zoom levels (they're useless and text overlaps anyway)
I'm not sure what the issue here is - the algorithm for selecting points should run just as fast and get roughly the same number of points when it's been running for 10 minutes. Is the amount of memory we're allocating in our
Float64Arrays causing Chrome problems?Proposed fixes should be tested in other browsers too (Chrome, Firefox, Safari)