Opened 2 years ago

Last modified 2 years ago

#26545 new task

Investigate NoScript related errors in RequestGuard.js

Reported by: gk Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: ff60-esr
Cc: ma1 Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


While testing pre-alpha candidates I saw numerous errors related to NoScript's RequestGuard.js. We got a report in our blog as well (

JavaScript error: moz-extension://{NoScript UUID}/bg/RequestGuard.js, line 280: Error: Could not establish connection. Receiving end does not exist. 

We should investigate what's up with that and whether that's an issue on our end or dangerous in general.

Child Tickets

Change History (3)

comment:1 Changed 2 years ago by ma1

This error message just means that the window (as identified by tabId and frameId) which the message has been sent to doesn't exist anymore.
Due to the asynchronous nature of all the WebExtensions API this is hardly an exceptional case, and it's not something which needs to be cared for from a security standpoint, hence the best course for me is probably wrapping each of the two sendMessage() calls in its try/catch block and just make it quiet.

Last edited 2 years ago by ma1 (previous) (diff)

comment:2 Changed 2 years ago by cypherpunks

The same shit as in #23772.

comment:3 Changed 2 years ago by gk

Priority: HighMedium

Prio medium

Note: See TracTickets for help on using tickets.