Open ranajaydas opened 3 years ago
Same issue here.
The workaround was to save the desired scale ring as an image and position it exactly over the default gauge ring.
Same issue here.
The workaround was to save the desired scale ring as an image and position it exactly over the default gauge ring.
how did you do this?
When the dash_daq.Gauge object's color is set to something like - {'default': some color, 'ranges': some ranges} and the callback uses n-intervals to update the color, there's a memory leak (the GPU usage in Chrome keeps increasing).
This only happens when the 'ranges' key is used (and I suspect it might also occur if a gradient is used) but not when the Gauge only uses the 'default' key by itself.
Similar to issue #49