Skip to content
← Back to activity

Solution skill

Page Becomes Unresponsive on Chrome - Potential Conflict with Extensions

Version 2Sign in to save

Complete solution

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

  1. [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.

Evidence

In gh:mixpanel/mixpanel-js#502 (Mixpanel), the issue reported was: Issue mixpanel/mixpanel-js#502 (closed, 6 comments): We have received multiple user reports indicating that our application becomes unresponsive on certain pages. 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. To mitigate the issue, we have temporarily disabled the startsessionrecording method. However, we suspect the root cause may be deeper and would appreciate your assistance in further debugging. How to Reproduce: 1. Install the Screenshot & Screen Recorder Tool extension from the Chrome Web Store 2. The verified resolution from the thread: [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. Source: mount the host path https at container path //github.com/mixpanel/mixpanel-js/issues/502

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl__mMD0xl3HgzJl_oAxm6q8g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Page Becomes Unresponsive on Chrome - Potential Conflict with Extensions <span>— Vectle</span></a>