Matthew Hodgson

Another datapoint: i set Nightly running again, breakpointed in persistSyncData, and `JSON.stringify(roomsData).length` is 143988497 bytes - so ~140MB, which really shouldn't be enough (even if allocated twice while bouncing back...

An argument against overlapping persists is the fact that the memory seems to explode very rapidly (e.g. before the inspector can notice, assuming it's updating every second, as one would...

So, my debug electron build is borked somehow - the Renderer immediately crashes with: ``` 3 libsystem_c.dylib 0x1af449d48 __stack_chk_fail + 96 4 Electron Framework 0x30c06d14c content::RenderFrameImpl::PrepareFrameForCommit(GURL const&, blink::mojom::CommitNavigationParams const&) +...

(It didn't crash overnight. Worth noting that the sync accumulator size has shrunk to 118103281 from 143988497 thanks to it being a fresh login - which might be enough of...

> It appears [v8 shares GC work between threads](https://v8.dev/blog/concurrent-marking), so if the OOM is occurring during GC, the crashing thread might not be the thread making the large number of...

This could be the same bug which is causing grey tiles in matrix-video-chat (https://github.com/vector-im/matrix-video-chat/issues/211)

Another option would be to just have it skip to the most recent unread message (before your current block) rather than the oldest.

The more I think about this, the more i think the solution is simply to have the 'jump to unread messages' banner take you up to wherever the RM is...

I think the only reason we didn't do this in the first place was because of concern that the RM gets flushed whenever you start reading a room, so you...

> The only alternative i can see is the whole enchilada over at #6483. Another possibility (which is like a lightweight version of #6483) would be to track the previous...