mirror of
https://github.com/gorhill/uBlock.git
synced 2024-11-10 09:07:54 +01:00
Fix handling of no-longer-existing port condition
The condition has been spotted occurring when bringing up the DOM inspector for a page on which cosmetic filters are being applied. Not clear why this happens, but uBO must be ready to graciously handle such condition.
This commit is contained in:
parent
262a1a044f
commit
4d68d7f586
1 changed files with 6 additions and 2 deletions
|
@ -959,7 +959,7 @@ vAPI.messaging = {
|
|||
try {
|
||||
port.postMessage(messageWrapper);
|
||||
} catch(ex) {
|
||||
this.ports.delete(port.name);
|
||||
this.onPortDisconnect(port);
|
||||
}
|
||||
}
|
||||
},
|
||||
|
@ -985,7 +985,11 @@ vAPI.messaging = {
|
|||
msg.tabId = tabId;
|
||||
for ( const { port: toPort } of this.ports.values() ) {
|
||||
if ( toPort === port ) { continue; }
|
||||
toPort.postMessage(request);
|
||||
try {
|
||||
toPort.postMessage(request);
|
||||
} catch (ex) {
|
||||
this.onPortDisconnect(toPort);
|
||||
}
|
||||
}
|
||||
break;
|
||||
case 'connectionBroken':
|
||||
|
|
Loading…
Reference in a new issue