Browser Extension Console Noise

Why this matters

During local debugging, browser extensions may inject scripts that print warnings/errors in DevTools.
Typical examples:

• contentscript.js
• ObjectMultiplex - orphaned data for stream ...
• MaxListenersExceededWarning

These messages often come from wallet or helper extensions, not from this project code.

Quick triage checklist

Use this checklist before creating a bug ticket:

1. Check stack/file origin

• If the stack points to contentscript.js or extension internals, treat it as extension noise first.
• If the stack points to src/... in this repo, treat it as project bug.

2. Reproduce in Incognito (extensions disabled)

• Open the same page in an incognito window with extensions disabled.
• If the warning disappears, it is extension noise.

3. Reproduce in a clean browser profile

• Use a temporary profile without extensions.
• If issue disappears, do not file as product defect.

4. Validate functional impact

• If page behavior is normal and only console logs exist, mark as non-blocking noise.
• If there is real UI/API failure, continue product-level debugging.

Team workflow (required)

When reporting frontend runtime issues:

1. Attach screenshot with call stack.
2. State whether test was done in incognito/clean profile.
3. Include one of:

• Extension noise confirmed
• Project bug confirmed (stack in src/...)

Without this info, issue should not be escalated as product bug.

Optional local filtering tips

• Keep a dedicated browser profile for development with minimal extensions.
• In DevTools Console, hide verbose logs from known extension sources.
• Prioritize errors that reference project paths under src/.