13454 - [IME/rule]JA input into the message body makes apprunner crash

Status: VERIFIED DUPLICATE of bug 15310

(MailNews Core :: Internationalization, defect, P2)

Description

[marina]

As soon as you turn ja IME and start tyoing into the body apprunner crashes
Steps to reproduce:
-open new Mail Composition window:
-type your email address;
-turn JA IM on;
-impossible to input into the Subject field (an other bug);
-proceed to the mail body;
-start typing;
//note: apprunner crashes

Comment 1

[Katsuhiko Momoi]

In yesterday's Win32 build, Japanese IME is disabled when the cursor is
placed in the Message Compose window.
Also this is a regression from builds from last week (e.g. 9/2/99 Win32
build).

Comment 2

[Katsuhiko Momoi]

Raising the priority and severity and setting TM to M11.

Comment 3

[Katsuhiko Momoi]

Crash does not occur on the regular HTML editor (though it has other
problems).

Comment 4

[Katsuhiko Momoi]

CC'ing ducarroz. The problem can be avoided if you first input some
ASCII character, e.g. a space before you begin Japanese input.
This also does not occur with Plain text Editor.

Comment 5

[Katsuhiko Momoi]

Now that the GFX is turned on, the same problem happens
when you try to input JPN into the subject field when ceratin
coditions are met as follows:

1.It seems that whe the cursor is placed in Subject filed,
  there is an ASCII space offset at the beginning. Sometimes
  the cursor get placed after the automatcially placed space
  and sometimes it doesn't. When the cursor is placed before
  the space, the crash occurs. Otherwise it doesn't.
2. It seems that when you first input elsewhere, e.g. the
   To field, or when you change the menu encoding to Japanese
   prior to inputting into the Subject field, the cursor seems
   to be placed more often after the space -- but this is not
   always true.

I have not observed this type of cursor placement in the text body
window and there you need to manually insert a space to avoid the crash.

By the way, To field does not seem to insert automatic space
when the cursor is placed in that field.

Comment 6

[lchiang]

(product is MailNews and target milestone is M11 or M12 - add to mail beta
tracking bug)

Comment 7

[msanz]

Tague, can you mark this bug M10, since this is a blocker for the next
milestone? Thanks

Comment 8

[msanz]

Marking M10 blocker as per seamonkey-leads meeting. This bug needs to be fixed
before M10 is released

Comment 9

[chris hofmann]

moving to m11.  let me know if fixes become available in the next few days
and can try to get them on the branch.

Comment 10

[Teruko Kobayashi]

I created the stack trace.

Talkback incident # 14006295
 Trigger Type:  Program Crash

 Trigger Reason:  Access violation
 Call Stack:    (Signature = IMETextTxn::Do aec6bea8)
   IMETextTxn::Do

[d:\builds\seamonkey\mozilla\editor\base\IMETextTxn.cpp, line 85]
   nsTransactionItem::Do

[d:\builds\seamonkey\mozilla\editor\txmgr\src\nsTransactionItem.cpp, line 104]
   nsTransactionManager::BeginTransaction

[d:\builds\seamonkey\mozilla\editor\txmgr\src\nsTransactionManager.cpp, line
1040]
   nsTransactionManager::Do

[d:\builds\seamonkey\mozilla\editor\txmgr\src\nsTransactionManager.cpp, line
137]
   nsEditor::Do

[d:\builds\seamonkey\mozilla\editor\base\nsEditor.cpp, line 344]
   nsEditor::SetInputMethodText

[d:\builds\seamonkey\mozilla\editor\base\nsEditor.cpp, line 3090]
   nsHTMLEditor::SetCompositionString

[d:\builds\seamonkey\mozilla\editor\base\nsHTMLEditor.cpp, line 3558]
   nsTextEditorTextListener::HandleText

[d:\builds\seamonkey\mozilla\editor\base\nsEditorEventListeners.cpp, line 1236]
   nsEventListenerManager::HandleEvent

[d:\builds\seamonkey\mozilla\layout\events\src\nsEventListenerManager.cpp, line
755]
   nsDocument::HandleDOMEvent

[d:\builds\seamonkey\mozilla\layout\base\src\nsDocument.cpp, line 2343]
   nsHTMLHtmlElement::HandleDOMEvent

[d:\builds\seamonkey\mozilla\layout\html\content\src\nsHTMLHtmlElement.cpp,
line 188]
   PresShell::HandleEvent

[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2078]
   nsView::HandleEvent

[d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 828]
   nsView::HandleEvent

[d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 813]
   nsView::HandleEvent

[d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 813]
   nsView::HandleEvent

[d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 813]
   nsViewManager::DispatchEvent

[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1667]
   HandleEvent

[d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 63]
   nsWindow::DispatchEvent

[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 342]
   nsWindow::DispatchWindowEvent

[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 359]
   nsWindow::HandleTextEvent

[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3608]
   nsWindow::ProcessMessage

[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2783]
   nsWindow::WindowProc

[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 448]
   USER32.dll + 0x1777 (0x77e41777)

Comment 11

[Frank Tang]

same stack trace as 15310

*** This bug has been marked as a duplicate of 15310 ***

Comment 12

[Katsuhiko Momoi]

Marked dependency on Bug 15310. Check when that bug is fixed.
Verification postponed until then.

Comment 13

[marina]

verified as such