Closed
Bug 178690
Opened 22 years ago
Closed 20 years ago
Crash on reply
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: 2009-bugzilla, Assigned: bugzilla)
References
Details
(Keywords: crash)
When replying to incoming mails mozilla crashes. Talkback IDs: TB13591552Y, TB13412851G, TB13049411Q, TB12953446X, ... As you will see these incidents are with Mozilla 1.1. But we currently can't change to a nightly build or 1.2b because it's a productive environment. Perhaps you can tell us if this bug is fixed in 1.2b or 1.0.1 ?
Assignee | ||
Comment 1•22 years ago
|
||
From talkback TB13591552Y: nsDocument::SetDocumentCharacterSet [c:/builds/seamonkey/mozilla/content/base/src/nsDocument.cpp, line 1023] nsEditor::SetDocumentCharacterSet [c:/builds/seamonkey/mozilla/editor/libeditor/base/nsEditor.cpp, line 920] nsPlaintextEditor::SetDocumentCharacterSet [c:/builds/seamonkey/mozilla/editor/libeditor/text/nsPlaintextEditor.cpp, line 264] nsEditorShell::SetDocumentCharacterSet [c:/builds/seamonkey/mozilla/editor/composer/src/nsEditorShell.cpp, line 2326] nsMsgCompose::SetEditor [c:/builds/seamonkey/mozilla/mailnews/compose/src/nsMsgCompose.cpp, line 1248] [snap]
Reporter | ||
Comment 2•22 years ago
|
||
Does still appear in 1.2 (Build 20021130), but not as often : TB15583646K, TB15439545K
Comment 3•22 years ago
|
||
Reporter, are you still seeing this in Mozilla 1.3 beta or later?
Reporter | ||
Comment 4•22 years ago
|
||
We cannot use alpha or beta versions at work, so - expect an answer when 1.3 has been released.
Comment 5•21 years ago
|
||
I'm getting crashes when forwarding and replying under v1.5 under Windows XP. I got it under v1.5rc1 as well, but not before that. It is not always reproduceable.
Comment 6•20 years ago
|
||
unable to reproduce with win Mozilla 1.7 beta.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•