Depending on timing, if chrome-extension-async's subscription (using chrome.runtime.onMessage.addListener) picks up an event not meant for it we sometimes get an error:
Error: The message port closed before a response was received.
This only seems to happen when the other onMessage listener returns false and tries to sendResponse, as such it's a side effect of another exception, and probably isn't worth working around.
Depending on timing, if
chrome-extension-async
's subscription (usingchrome.runtime.onMessage.addListener
) picks up an event not meant for it we sometimes get an error: