Async sendResponse from BG page, does not always send response to content script

Not reproducible Issue #10276331


Snehal G.
Dec 20, 2016
This issue is public.
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

  1. We have an extension that has bunch of BG scripts and send response to load our UI
  2. Some of them are async sendResponse’s.
  3. These async calls work sometimes, and do not work most of the times.
  4. sendReponse from BG page is not able to send message to our UI script (content script)


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

    • Do you have a sample extensions handy we can use for testing these async failures?

    • Very similar behaviour is happening to me. Async sendResponse works for a while and then suddenly breaks - all of the responses received in callbacks in content script via sendMessage(data, callback) are undefined.

      I’d provide a sample but I haven’t been able to track down the culprit just yet.

    • Hi Michael, what build are you running on? If you’re running on the Anniversary Update (14393), it sounds like you might be running into the following issue which has since been fixed in recent Windows Insider Program builds:

      There is a workaround in the discussion section of that bug if this is the issue you’re running into, otherwise any other repro steps you could provide to help us narrow down the issue would be greatly appreciated. Thanks!

    • Microsoft Edge Team

      Changed Assigned To from “Brad E.” to “Scott L.”

      Changed Status to “Not reproducible”

    • I’ve created a sample extension that uses sendResponse in both content/background script communication and popup/background communication. Unfortunately, I have not been able to reproduce any issues on the latest Windows Insider Preview builds. As a result, I am going to resolve this bug as “Not Reproducible” for the time being. If you manage to hit this on Windows Insider Preview builds, please feel free to reopen this bug with any relevant information you have and I will investigate further. Thanks!

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

    Sign in