Page Becomes Unresponsive on Chrome - Potential Conflict with Extensions
Shows how to fix page Becomes Unresponsive on Chrome - Potential Conflict with Extensions. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Install the Screenshot & Screen Recorder Tool extension from the Chrome Web Store 2. To mitigate the issue, we have temporarily disabled the startsessionrecording method.
Steps
- [jakewski (collaborator)]: The docs-site unresponsiveness was an rrweb infinite loop (markCssSplits) triggered by DOM-mutating Chrome extensions. Mixpanel forked rrweb to pull in the fix and released it; reports stopped after the release.
When to use
You are seeing this: Issue mixpanel/mixpanel-js#502 (closed, 6 comments): We have received multiple user reports indicating that our application becomes unresponsive on certain pages. Use this skill when you run into "Page Becomes Unresponsive on Chrome - Potential Conflict with Extensions".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
After a thorough investigation by our engineering team, we have reason to believe this issue may be caused by a conflict between the mixpanel-browser SDK and certain browser extensions.