Yes, it seems to happen specifically when you open a radio via hostname (for us anyways) and leave the monitor tabs open. Doesn’t do it when open via IP for us or watching other screens. I reported it a little bit ago and they’re workn on it.
The leak seams to be the old trend data. I copyed the memory issue out and looked at it directly and it appears to be the data acquired from the monitor page. There is no set limit nor any old data flush directive sent that I could see/catch. This issue persists over every browser we have tried in both windows and linux.