Closed Bug 176505 Opened 22 years ago Closed 22 years ago

Composer dead : An error occured while creating a message compose window. Please try again. [

Categories

(SeaMonkey :: Composer, defect)

Product:
SeaMonkey
Component:
Composer
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: tracy, Assigned: cmanske)

References

Details

(Keywords: regression, smoketest, Whiteboard: EDITORBASE)

Attachments

(1 file, 3 obsolete files)

update packages-*
1.56 KB, patch
sfraser_bugs
: review+
kinmoz
: superreview+
Details | Diff | Splinter Review 
seen on commercial trunk builds:

windows 2002-10-24-04-trunk
linux 2002-10-24-04-trunk
mac os9 2002-10-24-03-trunk

-Open a new composer window. 
Very few menu itmes seem to be working

-browse a page in navigator
-select File | Edit Page
a blank composer window opens (also dead)
Keywords: smoketest
any js errors? like the one posted in bug 176493?
context menus are working fine for me.  I don't have a java console open.

this is also blocking mail composition.
confirming....Composer is totally dead. can't do anything...I'm using today's
trunk build.
Keywords: nsbeta1, regression
Whiteboard: EDITORBASE
What do "very few items seem to be working" and "blank" mean?  Are the toolbars
missing?  Greyed out?  Enabled, but clicking on them does nothing?  My tree is
still building, but having some clue what the failure is might help in looking
at checkins.
The Tool bar buttons don't call the expected dialogs in cases such as Image, 
Table or Link.  The Drop down menus look fine but anything that actually does 
something in the compose area doesn't work.  ie Debug |Insert text. Text cannot 
be typed into the composer window, you can't get focus there.
for mozilla.exe -edit:
no title
doesn't appear in window list
the only disabled button i have is spell (i can imagine why)
clicking the color foreground and odd widget (but not the behind foreground
widget) results in a dialog which works except that ok doesn't actually change
anything :)
justification buttons respond but with no content it's useless :)
font size+/-, bold/italic/underline, bullets, numbered list, indent, outdent, do
nothing.
switching tabs doesn't do anything. source view doesn't happen, it look like the
other empty views. html tags doesn't show [body]
the only file items that work are new> and probably exit.
nothing in edit works
view works
nothing in insert works
->brade to triage
Assignee: syd → brade
Kathy's on vacation; I'll take it.  So far I've tried backing out all the
suspicious looking checkins, and nothing helps.  Now I'm backing out the
unsuspicious looking ones ...
Assignee: brade → akkana
Blocks: 176535
Um, it would help if I had cc'ed jag on that last comment, since we're going to
have to back this out ...
Attached patch the backout (obsolete) — — Splinter Review 
In case anyone wants it, here's what I backed out.
The backout is in, so to speak.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
I updated with the backed out checkin, as it were, and it didn't fix the problem
for me. nsFrameFrame.cpp was rebuilt, and gklayout.dll, but I still can't bring
up the mail compose window, or type into composer. And I'm still getting
domevent listener errors when I select a folder that make it difficult to use
mail. From what I can tell, we're not out of the woods yet.
*** Bug 176520 has been marked as a duplicate of this bug. ***
I didn't get FrameLoader - it doesn't show up as checked in with Tinderbox. I'll
doublecheck.
I should say, bonsai didn't show it as checked in. Tinderbox does show it as
checked in. Sorry for the confusion.

http://bonsai.mozilla.org/showcheckins.cgi?&treeid=SeaMonkey
*** Bug 176566 has been marked as a duplicate of this bug. ***
Right, that's why this bug took so long to fix: bonsai doesn't show the file
that was causing the problem, so I wasted two hours backing out 20 other files
before Kin finally noticed that Tinderbox was showing files that Bonsai didn't.
 Dawn, why is that?  They're in the same directory, so surely they're part of
the same module?
I changed the bug summary to something less generic. Hopefully this generates
more hits in a query and less duplicates
Summary: Composer dead → Composer dead : An error occured while creating a message compose window. Please try again. [
*** Bug 176592 has been marked as a duplicate of this bug. ***
verified fixed on commercial trunk builds:

windows 2002-10-25-04-trunk
linux 2002-10-25-04-trunk
mac osx 2002-10-25-03-trun
Status: RESOLVED → VERIFIED
Seeing this again on 2002111221 on Linux Mandrake 9. Did not happen with a build
from about a week ago. Didn't see this on Win2k SP3 or WinXP SP1 on Nov 11 builds.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
I don't see any problems with my mac debug build from last night
WFM Win2k 2002111304
this is broken for me on my trunk build pulled last night. Here's the js error:

************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "'[JavaScript Error: "window.editorShell has no properties" {file:
 "chrome://messenger/content/messengercompose/MsgComposeCommands.js" line: 236}]
' when calling method: [nsIMsgComposeRecyclingListener::onReopen]"  nsresult: "0
x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame ::
chrome://messenger/content/mailNavigatorOverlay.xul :: openComposeWindow :: line
 63"  data: yes]
************************************************************

since the editorShell was removed, it's not shocking that this error is getting
generated.
*** Bug 179920 has been marked as a duplicate of this bug. ***
never mind - it works for me; my build failed and rebuilding mailnews fixed it.
Hopefully, once all testers get the latest builds, these problems will clear up.
Assignee: akkana → cmanske
Status: REOPENED → NEW
David Bienvenu sees the problem on the packaged build he downloaded (Windows).
Mac packaged build from 3am doesn't seem to have the problem.
*** Bug 179931 has been marked as a duplicate of this bug. ***
bringing up composer generates a couple js errors in my mozilla nightly release
build:

Error: uncaught exception: [Exception... "Could not convert JavaScript argument
(NULL value cannot be used for a C++ reference type) arg 0
[nsIInterfaceRequestor.getInterface]"  nsresult: "0x8057000b
(NS_ERROR_XPC_BAD_CONVERT_JS_NULL_REF)"  location: "JS frame ::
chrome://global/content/bindings/editor.xml#editor.editingSession (getter) ::
onget :: line 0"  data: no]

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]"  nsresult: "0x80004002
(NS_NOINTERFACE)"  location: "JS frame ::
chrome://editor/content/ComposerCommands.js :: GetComposerCommandManager :: line
229"  data: no]


Confirming that damn bug is back. I have all CVS patches until 7:45 one.

What broke again composition window ?
Is this because we are missing composer.xpt in the packaging scripts?
wfm with win2k and a 15min old CVS trunk clobber build and modern Theme
I am only seeing this on windows and linux from this morning; both mac os9 and
osx are fine.  The mac builds kicked off at 3:00am while linux and windows
kicked off at 4:00am.  Hope that helps.
Attached patch Possible short term fix. (obsolete) — — Splinter Review 
I can recreate the problems bienvenu sees by removing composer.xpt from my
dist/bin/components dir.

I think nsIEditingSession.idl should be in editor.xpt anyways, so this patch
just places it there. IMO, it probably shouldn't live under composer.
Comment on attachment 106107 [details] [diff] [review]
Possible short term fix.

r=brade
Attachment #106107 - Flags: review+
Comment on attachment 106107 [details] [diff] [review]
Possible short term fix.

sr=bienvenu
Attachment #106107 - Flags: superreview+
> I think nsIEditingSession.idl should be in editor.xpt anyways
Why?
Ok, we had a pow-wow on IRC, and decided go the packaging route for now. Mac
will need to be fixed sometime so that it is consistent with the other platforms
in terms of creating a separate composer.xpt.
Attached patch update packages-* (obsolete) — — Splinter Review 
i updated packages-mac, too, for the future, when composer.xpt is generated
(adding it now will produce warnings, but avoid future errors when composer.xpt
starts getting built on mac).
i updated packages-mac, too, for the future, when composer.xpt is generated
(adding it now will produce warnings, but avoid future errors when composer.xpt
starts getting built on mac).
Attachment #106107 - Attachment is obsolete: true
Attachment #106115 - Attachment is obsolete: true
Comment on attachment 106116 [details] [diff] [review]
update packages-*

sr=kin@netscape.com
Attachment #106116 - Flags: superreview+
committed.
Status: NEW → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
*** Bug 179957 has been marked as a duplicate of this bug. ***
This doesn't fix my build, in case anyone cares.  Neither composer nor mail
compose work.  I'm pulling a fresh build now in case that helps.
Attachment #104017 - Attachment is obsolete: true
verified fixed with respins:

windows 2002-11-13-08-trunk
linux 2002-11-13-13-trunk
Status: RESOLVED → VERIFIED
A freshly pulled tree cured the problems I was seeing.  No idea what file was
causing the problem in the old tree.
Sorry, but composition window is again broken. I grabbed CVS patches (all from
13 november), and build mozilla, and now, no address in From bar :-[

What is happening ?!

I cannot understand :-|

Should I have to reopen this bug or what ?
*** Bug 190436 has been marked as a duplicate of this bug. ***
Still have this problem in 1.4 release of mozilla, can I resolve it without
create a new user profile and reset everything?
Did you try deleting XUL.mfl from your user profile directory? Sometimes that
gets corrupted and leads to strange problems.
Have read this thread before:
http://groups.google.com/groups?hl=zh-TW&lr=&ie=UTF-8&threadm=d817c73e.0307040119.109169d4%40posting.google.com&rnum=3&prev=/groups%3Fq%3Dcarfield%2Byim%26sa%3DG%26scoring%3Dd

And tried to delete XUL.mfl, but still don't help.

I know it will be hard for mozilla team to debug, how can I get more trace
message for you?
Re: comment #53: if anyone knows of strangeness fixed by removing the FastLoad
file, please file a bug.

/be
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: