Description
Environment
SaaS (https://sentry.io/)
Version
No response
Link
No response
DSN
No response
Steps to Reproduce
We enabled Sentry Replay, but after an hour in production, we had to revert this change. Customers with a large number of displayed rows on a single page (in our case, a huge list of room types) were starting to report that the page was slowing down a lot, freezing, and had bad performance after some clicks. We were able to reproduce this problem only on a branch with Sentry Replay enabled.
It seems that where the DOM tree is huge (250k nodes), then the way Sentry Replay stores data in the browser starts to slow down whole tab (other tabs in browser work OK)
On my example when I click on "choose" button page freezing for 2-5 minutes.
Number of DOM nodes is duplicated twice - from 250k to 500k nodes.
Expected Result
No freezing
Actual Result
Console output from Chrome Developer Tool:
Performance tab from Chrome Developer Tool:
As you see on the last two pictures Sentry is the one who eat resources