[BUG] Memory Leak - dash_daq.Gauge when using custom range for the color

[ranajaydas]

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

[yuribr84]

Same issue here.

The workaround was to save the desired scale ring as an image and position it exactly over the default gauge ring.

[notron30]

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?