Communication between content script and background page is broken with large messages (runtime.connect)

Fixed Issue #19445073


Damien R.
Oct 29, 2018
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 7 people

Sign in to watch or report this issue.

Steps to reproduce


Issue found in the insider preview version of Edge (44.18267.1001.0).
It works fine in the currently live Edge version (42).

We found that sending twice a string longer than 4195 characters will
indefinitely break the Runtime.Port instance (and all future instances for that

We created an extension to replicate the issue, you can find it here (the unexpected behavior is also detailed inline in the comments of the content script).

See also the attach video that exhibits the issue with that test extension.

I am available to help you move forward with this issue (mail, screenshare, phone call, anything), this issue is critical for the company I work for, and our Edge users.

Best regards.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Veerabhadra r.”

  • Hi, Thanks for reporting your feedback. We tested it and suggesting you please direct to and ask them to open a support incident to work one of engineer on this issue.

    The MS Edge Team.

  • Hi,

    I’m not going to do that.
    Please forward this issue to the appropriate person within the Edge team.

    Thank you.

  • Microsoft Edge Team

    Changed Assigned To to “Arvind M.”

    Changed Assigned To from “Arvind M.” to “Mahesh J.”

    Changed Assigned To from “Mahesh J.” to “Utkarsh P.”

    Changed Status to “In code review”

    Changed Status from “In code review” to “Fixed”

You need to sign in to your Microsoft account to add a comment.

Sign in