Critical bug in chrome.tabs.sendMessage for a "Sleeping" tab in Edge browser #134
Labels
Bug
the issue is a code defect that should be fixed
Investigating
The reported bug or issue is being actively investigated
Waiting for more info
more information is needed and the reporter was at-mentioned.
Hi, I don't know where to report this because this issue is specific to the Edge browser (Chrome doesn't have a Sleeping tabs feature - and it's Memory Saver feature works correctly).
Steps to reproduce issue:
await chrome.tabs.query({})
to get all open tabschrome.tabs.sendMessage(tabId, { type: 'check', }, { frameId: 0 }).then(x => console.log('responded', x)).catch(x => console.log('errored', x))
Expected result: promise resolves/rejects with an error message like "Receiving end does not exist".
Actual result: promise remains in pending state until the tab is woken up from sleep.
Request: I think this is a bug and we should fix this, but at the very least, there should be a property on the Tab object indicating that this tab is sleeping (so the extension doesn't bother messaging the tab). On Chrome, the
discarded
property is set to true for a tab that is crashed by the Memory Saver.This seems to be a Edge specific issue in Extension APIs. Please let me know what is the appropriate forum to report this issue.
The text was updated successfully, but these errors were encountered: