Error: Could not establish connection. Receiving end does not exist.

[sentry-io]

Sentry Issue: METAMASK-X99M

Error: Could not establish connection. Receiving end does not exist.

This issue has a high volume (~40K errors/day) and often triggers the "+100% raise of old Sentry issues over the past 24h " alert in #metamask-extension-release-monitoring Slack channel. We shall treat it as a sev2.

[Gudahtt]

No obvious user impact, but labelling this as sev2 because of the high Sentry volume (this is currently the most frequent error by a significant margin).

[gauthierpetetin]

We looked at this issue with @MetaMask/extension-platform during technical refinement today and didn't find a lot to investigate on while looking at what's in Sentry.

It's not a new issue as it was first seen 5 months ago. @seaona has seen this error several times, without being able to identify clear reproduction steps. She only encountered this on MV3 Extension, not MV2.

This issue seems related as well: #15970

Here's also a screenshot of the logs @seaona 's got in her console when the issue occurred:

[NiranjanaBinoy]

Reproduction steps:

1. Load the app
2. open the service worker console.
3. Now open the metamask app
4. We can see Error: Could not establish connection. Receiving end does not exist. in the console, almost consistently.

[gauthierpetetin]

Thanks for investigation @NiranjanaBinoy .
There's also this comment in the onDisconnectDestroyStreams function in the code that I'll add below in case it's useful:

If an error is found, reset the streams. When running two or more dapps, resetting the service
worker may cause the error, "Error: Could not establish connection. Receiving end does not
exist.", due to a race-condition. The disconnect event may be called by runtime.connect which
may cause issues. We suspect that this is a chromium bug as this event should only be called
once the port and connections are ready. Delay time is arbitrary.