Closed
Bug 17689
Opened 25 years ago
Closed 25 years ago
[DOGFOOD][BLOCKER] Crash with gfx text controls
Categories
(Core :: DOM: Editor, defect, P1)
Core
DOM: Editor
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: mscott, Assigned: buster)
References
Details
(Whiteboard: [PDT+])
I mistyped my imap password into the password dialog. I got the message from
the imap protocol saying the log in failed. And then before we brought up
another password dialog, I crashed in nsHTMLEditor::nsHTMLEditor
because a global variable: gTypingTxnName was pointing to an object that had
been deleted.
I'll try to verify my steps again but wanted to log the stack trace before I
restarted.
Note: this was with a tree pulled this morning (11/01).
Here's the stack trace:
nsHTMLEditor::nsHTMLEditor() line 217 + 14 bytes
nsHTMLEditorLog::nsHTMLEditorLog() line 38 + 15 bytes
CreateNewEditor(nsISupports * 0x00000000, const nsID & {...}, void * *
0x0012dbe4) line 115 + 30 bytes
nsGenericFactory::CreateInstance(nsGenericFactory * const 0x03325b60,
nsISupports * 0x00000000, const nsID & {...}, void * * 0x0012dbe4) line 38
nsComponentManagerImpl::CreateInstance(nsComponentManagerImpl * const
0x01014350, const nsID & {...}, nsISupports * 0x00000000, const nsID & {...},
void * * 0x0012dbe4) line 1261 + 24 bytes
nsComponentManager::CreateInstance(const nsID & {...}, nsISupports * 0x00000000,
const nsID & {...}, void * * 0x0012dbe4) line 78
nsGfxTextControlFrame::CreateEditor(nsGfxTextControlFrame * const 0x0352d620)
line 175 + 43 bytes
nsGfxTextControlFrame::CreateSubDoc(nsRect * 0x00000000 {x=??? y=??? width=???
height=???}) line 536 + 21 bytes
nsGfxTextControlFrame::SetFocus(int 1, int 1) line 922 + 20 bytes
nsHTMLInputElement::HandleDOMEvent(nsHTMLInputElement * const 0x032fd3dc,
nsIPresContext & {...}, nsEvent * 0x0012de48, nsIDOMEvent * * 0x00000000,
unsigned int 1, nsEventStatus & nsEventStatus_eIgnore) line 623
nsEventStateManager::SendFocusBlur(nsEventStateManager * const 0x0352d030,
nsIPresContext * 0x032d6080, nsIContent * 0x032fd3dc) line 1520
nsEventStateManager::SetContentState(nsEventStateManager * const 0x0352d030,
nsIContent * 0x032fd3dc, int 2) line 1384
nsHTMLInputElement::SetFocus(nsHTMLInputElement * const 0x032fd3e4,
nsIPresContext * 0x032d6080) line 539
nsHTMLInputElement::Focus(nsHTMLInputElement * const 0x032fd3d0) line 517 + 25
bytes
HTMLInputElementFocus(JSContext * 0x03503750, JSObject * 0x02676e40, unsigned
int 0, long * 0x0268cd14, long * 0x0012e108) line 840 + 15 bytes
js_Invoke(JSContext * 0x03503750, unsigned int 0, unsigned int 0) line 672 + 26
bytes
Reporter | ||
Updated•25 years ago
|
Summary: [DOGFOOD] Crash when entering password information → [DOGFOOD] Crash when entering password information
Reporter | ||
Comment 1•25 years ago
|
||
Yeah, these steps reproduce it every time for me. Mistype your password the
first time. Then hit okay when it tells you the login failed. After that
you'll see this crash
Reporter | ||
Updated•25 years ago
|
Summary: [DOGFOOD] Crash when entering password information → [DOGFOOD] Crash with gfx text controls
Reporter | ||
Comment 3•25 years ago
|
||
Actually this problem is much worse than just a problem with imap password
dialogs. I can't even bring up a web page that uses gfx text controls.
i.e. try loading bugzilla query in the browser with this mornings build
and you'll see exactly what I'm talking about.
Changing the subject to reflect the fact that this problem is more generic.
Reporter | ||
Comment 4•25 years ago
|
||
I said bugzilla query but what I really meant was viewing an existing bug in the
database. That always crashes for me.
adding ducarroz@netscape.com to cc: list
Severity: normal → blocker
OS: Windows NT → All
Hardware: PC → All
Summary: [DOGFOOD] Crash with gfx text controls → [DOGFOOD][BLOCKER] Crash with gfx text controls
This is really bad for mail because we crash when the password dlg comes up for
mail. See duplicate bugs for descriptions. I'm upgrading this severity to
blocker for now.
Assignee: beppe → buster
Priority: P3 → P1
Target Milestone: M11
Assignee | ||
Comment 10•25 years ago
|
||
already fixed in my tree, will check in tonight.
Comment 11•25 years ago
|
||
*** Bug 17696 has been marked as a duplicate of this bug. ***
Comment 12•25 years ago
|
||
Putting on PDT+ radar
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 13•25 years ago
|
||
fixed. r=floppy moose
Comment 14•25 years ago
|
||
*** Bug 17769 has been marked as a duplicate of this bug. ***
Comment 15•25 years ago
|
||
verified in 11/4 build.
Comment 16•25 years ago
|
||
linking to PDT+ tracking bug 12658
You need to log in
before you can comment on or make changes to this bug.
Description
•