Over time an open tab of misskey, especially deck view, slows down hugely (also making firefox use a lot of cpu i think)
Refreshing or closing and opening the tab solves this.
This occurs when leaving a single tab open for a number of hours, I think it is due to notes not being removed from the dom or something when they are off the screen/sufficiently old.
One potential fix is to make notes a certain distance off the length of a column get removed from the dom, and redownload/lazy load them if they are scrolled back down to.
Expected Behavior
Performance of tab stays the same over time
Actual Behavior
Performance reduces over time
Steps to Reproduce
Open a misskey instance in deck or home view in a tab
Leave tab open for a number of hours
Attempt to use misskey in that tab
Environment
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/67974320-performance-reduces-over-time?utm_campaign=plugin&utm_content=tracker%2F51027576&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F51027576&utm_medium=issues&utm_source=github).
Summary
Over time an open tab of misskey, especially deck view, slows down hugely (also making firefox use a lot of cpu i think) Refreshing or closing and opening the tab solves this. This occurs when leaving a single tab open for a number of hours, I think it is due to notes not being removed from the dom or something when they are off the screen/sufficiently old. One potential fix is to make notes a certain distance off the length of a column get removed from the dom, and redownload/lazy load them if they are scrolled back down to.
Expected Behavior
Performance of tab stays the same over time
Actual Behavior
Performance reduces over time
Steps to Reproduce
Environment