Joan León @nucliweb.net · May 16

I think I may have found a memory leak in LinkedIn A single browser tab was consuming 6 GB of RAM just from leaving the feed open for a while Possible causes: • client-side state leaks • excessive caching • unreleased media resources • runaway DOM growth Performance is a feature #WebPerf

8 likes 3 replies

?

Replies

John Allsopp · May 16

Oh yeah. It’s been happening forever!

Michael · May 17

Zero surprise. Their clients use implementation is a tangled web arstechnica.com/tech-policy/...

Joan León · May 16

Anyone else seeing this with LinkedIn or other large SPAs?