James Marsh

My personal project experiences memory problems without creating a new odata resource. I'll do more testing tomorrow and ill let you know how it goes.

creating the odata resource only once doesn't seem to help, The test at [http://jsfiddle.net/h22f7596/169/show/](http://jsfiddle.net/h22f7596/169/show/) still has the issue. I took out the filters and just did odata().query() and found that...

Looks like the memory increases depending on the size of the data set. Specifically the resourceStore array gets larger and larger the more requests are performed. What is the purpose...

@kyse Do you know how you would go about fixing this? I can take a look at it if you could point me in the right direction.

Adding the attribute decimal-places="1" to the range slider resolves this for me

I've had this issue crop up as well (1.82 and 1.83). It's not quite the same but I've added a repro of my problem here: https://godbolt.org/z/W1s7YEczP with the points plotted...

I've had this issue using float and double. I only managed to solve it by moving to cpp_bin_float_quad in boost multiprecision but that's crazy slow and I can't guarantee that...