If no listeners reply to chrome.runtime.onMessageExternal the callback doesn't fire
Reported by
to...@corevo.io,
Jan 16
(6 days ago)
|
|||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3669.0 Safari/537.36
Steps to reproduce the problem:
1. Install ext-a and ext-b in chrome
2. Open the console of the sender extension
3. Type in chrome.runtime.sendMessage('ext-b extension id', {}, () => {debugger;}) where you fill the extension id
What is the expected behavior?
The callback to fire and chrome.runtime.lastError to be set to
{message: "The message port closed before a response was received."}
What went wrong?
The callback never fires and chrome.runtime.lastError is undefined
Did this work before? Yes Still works in stable Chrome 71
Does this work in other browsers? Yes
Chrome version: 72.0.3626.53 Channel: beta
OS Version: OS X 10.14.2
Flash Version:
This still works in the stable channel, and will affect extensions installed on users machines once the beta channel hits production.
,
Jan 16
(6 days ago)
Bisected to r569277 = 0ef734f4659e2af652b6846e073be226cd11de6d = crrev.com/c/1108192 "[Extensions Bindings] Add a fieldtrial testing config entry for native bindings" Landed in 69.0.3469.0 Confirmed by observing no bug after running chrome --disable-features=NativeCrxBindings Bisected the underlying bug to r533360 = b15f7f04de19b4e835f7be615a1d488876f8d086 = crrev.com/c/860755 "[Extensions Bindings] Finish messaging-related implementations" Landed in 66.0.3336.0 FWIW, I'm attaching an automated repro; just edit the paths in the command and run it: chrome --enable-features=NativeCrxBindings --load-extension="path/to/ext-a","path/to/ext-b" It will display "GOOD" or "BAD".
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
This blocks the popular developer tool https://chrome.google.com/webstore/detail/selenium-ide/mooikfkahbdckldjjndioackbalphokd so I'm increasing priority to P1.
,
Today
(20 hours ago)
Able to reproduce the issue on reported version# 72.0.3626.53, stable# 71.0.3578.98 and latest chrome# 73.0.3679.0 using Mac 10.12.6, Ubuntu 14.04 and Windows-10, hence providing Bisect Info Bisect Info: ================ Good build: 66.0.3335.0 Bad build: 66.0.3336.0 Assigning to the suspect as provided in comment# 2 Change-Log: https://chromium.googlesource.com/chromium/src/+log/66.0.3335.0..66.0.3336.0?pretty=fuller&n=10000 Suspecting: https://chromium.googlesource.com/chromium/src/+/b15f7f04de19b4e835f7be615a1d488876f8d086 from above change log Change-Id: If09f607fe5c9f30578f84248173848b30c7bbf21 Reviewed-on: https://chromium-review.googlesource.com/860755 @Devlin Cronin: Please confirm the issue and help in re-assigning if it is not related to your change. Thanks! |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by phistuck@chromium.org
, Jan 16 (6 days ago)Labels: -Hotlist-Interop