Open Bug 1903747 Opened 5 months ago Updated 4 months ago

JavaScript error: chrome://messenger/content/messengercompose/MsgComposeCommands.js, line 11032: NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMsgCompose.initEditor]

Categories

(Thunderbird :: Message Compose Window, defect)

Product:
Thunderbird
Component:
Message Compose Window
Version:
Thunderbird 129
Type:
defect

Tracking

(Not tracked)

People

(Reporter: mkmelin, Unassigned)

References

(Blocks 1 open bug)

Details

JavaScript error: chrome://messenger/content/messengercompose/MsgComposeCommands.js, line 11032: NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMsgCompose.initEditor]

https://searchfox.org/comm-central/rev/4770a7ef205ca3cd702f92c87817948670a9feba/mail/components/compose/content/MsgComposeCommands.js#11072 (I think)

Happens e.g. during comm/mail/components/extensions/test/browser/browser_ext_compose_bug1882725.js

Hello Magnus,

Is there something QA can manually do in order to reproduce this issue?

If not, could you please update the affected version in Tracking Flags(if that applies)?

Thank you in advance!

Flags: needinfo?(mkmelin+mozilla)

These happen during CI try runs (see bug 1901695). No QA needed. The logs were during 129, but probably also older versions are affected.

Flags: needinfo?(mkmelin+mozilla)
Version: unspecified → Thunderbird 129
You need to log in before you can comment on or make changes to this bug.