NS_NOINTERFACE: Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface] stack-trace-collector.js:84
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: ishikawa, Unassigned)
Details
Attachments
(1 file)
|
243.62 KB,
image/png
|
Details |
I hit this while I use TB 32-bit under Windows 10 (64-bit).
observe(subject, topic, data) {
let channel, id;
try {
channel = subject.QueryInterface(Ci.nsIHttpChannel);
id = channel.channelId;
} catch (e) {
// WebSocketChannels do not have IDs, so use the URL. When a WebSocket is
// opened in a content process, a channel is created locally but the HTTP
// channel for the connection lives entirely in the parent process. When
// the server code running in the parent sees that HTTP channel, it will
// look for the creation stack using the websocket's URL.
channel = subject.QueryInterface(Ci.nsIWebSocketChannel); <=== this is line 84
id = channel.URI.spec;
}
if (!matchRequest(channel, this.filters)) {
return;
}
I have no idea why stack-trace-collector.js tries to use websocket channel.
But if it needs to access something from the net to provide stack trace(?) and
fails due to the net access issue because of missing interface, we are in trouble.
We can't have a reasonable stack trace in case of a serious error?
TIA
PS: I have opened error console for a while to try figuring out some other issues, and
forgot about the opened console when I realized these error lines.
I am attaching the screen capture of the error console.
Comment 1•6 years ago
|
||
I am running Thunderbird 68.10 on W10.
Today I suddenly had all emails being sent take about 2-4 minutes to complete sending.
Error comes up as:
NS_NOINTERFACE: Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface] stack-trace-collector.js
After about 3 minutes, the email is sent successfully.
No change performed on W10 or Thunderbird from yesterday.
Description
•