Closed Bug 1212604 Opened 11 years ago Closed 4 years ago

Repeated "Message: TypeError: this.sandbox is undefined" errors on console

Categories

(Add-on SDK Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: botond, Unassigned)

Details

I'm running Nightly on Debian. I get the following error being spewed on the console repeatedly during normal browser usage: console.error: Message: TypeError: this.sandbox is undefined Stack: receive@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/content/worker-child.js:75:7 emitOnObject@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/event/core.js:112:9 emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/event/core.js:89:38 processMessageReceived@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/remote/child.js:54:38 I didn't notice any corresponding loss of functionality.
Component: Untriaged → General
Product: Firefox → Developer Documentation
This has nothing to do with developer documentation on MDN.
Component: General → Untriaged
Product: Developer Documentation → Firefox
Component: Untriaged → Security
Product: Firefox → Core
this.sandbox is set by WorkerChild's "initialize" and nulled out by destroy(). Presumably we're getting a receive() called after destroy(). observe() has a null-check; I expect that receive() should too. None of this has anything to do with Core code; this is addon sdk stuff.
Component: Security → General
Product: Core → Add-on SDK
Thank you Boris. I will make note of that.

This bug lies at rest in the graveyard.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.