Performance issues in Chrome since 142

[nickvergessen]

Memory usage

• Up to 2 Gb RAM in Chrome accumulated during ongoing call
• Detached nodes left after hovering elements (chat messages, video tiles, call grid)
• Possible references for peers / streams are kept and not collected by GC

Expensive operations

• mouseover event listeners on elements (chat messages, video tiles, call grid)
• RecycleScroller - using GPU for rendering virtual list
• NcActions - a lot of recalculations (from composables)