Crash when using with Unispim Pinyin IME 3.0/4.0 [@ js_AllocStack]

RESOLVED INCOMPLETE

Status

()

Core
Internationalization
--
critical
RESOLVED INCOMPLETE
13 years ago
5 years ago

People

(Reporter: Hillin, Assigned: smontagu)

Tracking

({inputmethod})

Trunk
x86
Windows XP
inputmethod
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [needs retesting on Windows with Unispim Pinyin IME])

Attachments

(1 attachment)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051221 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051221 Firefox/1.6a1

While typing something in any of the textboxes in Firefox(no matter one in the UI or on the webpage) with Unispim Pinyin IME 3.0 or 4.0(m3), Firefox will crash when switching IME, sometimes even when the textbox lost focus(e.g. click on another button).

Reproducible: Always

Steps to Reproduce:
1.Install Unispim pinyin IME(version 3.0 could be downloaded at http://ftpgz13.pconline.com.cn/pub/download/200304/unispim30.exe).
2.Type any Chinese characters in any of the textboxes in Firefox(v1.5+).
Actual Results:  
Crash!

Expected Results:  
Apparently no crash.

This won't happen with Firefox 1.0.
Theme:Aquatine 1.6.4
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051221 Firefox/1.6a1 ID:2005122106
Could you send the crash report by talkback and tell me the incident ID?
Severity: normal → critical

Updated

13 years ago
Assignee: nobody → smontagu
Component: General → Internationalization
Keywords: stackwanted
Product: Firefox → Core
QA Contact: general → amyy
Version: unspecified → Trunk
(Reporter)

Comment 2

13 years ago
Created attachment 207051 [details]
The talkback detail

Well this is the detail file saved from the talkback program.
It is automatically sent for several times, evertime after the program crashes.

Comment 3

13 years ago
erm. that's useless, all we can use is the talkback incident id. the other stuff is provided so that you can see the unhelpful data precisely as it's sent to the server so that you don't decide that we're stealing confidential bits from you.

unfortunately, those bits are only meaningful to a server to which they're sent, where they're paired with other data. the only real way we can get anything useful is for you to run talkback.exe and tell us what the incident id is.
(Reporter)

Comment 4

13 years ago
But where is the incident ID? I can't really find it.
(Reporter)

Comment 5

13 years ago
Aha, found. It is shown in the Agent window.
The ID is:
TB13364769K

Comment 6

13 years ago
Incident ID: 13364769
Stack Signature	js3250.dll + 0x1cec9 (0x6009cec9) 5a0840b6
Product ID	FirefoxTrunk
Build ID	2005122206
Trigger Time	2005-12-28 20:25:38.0
Platform	Win32
Operating System	Windows NT 5.1 build 2600
Module	js3250.dll + (0001cec9)
URL visited	
User Comments	
Since Last Crash	3828 sec
Total Uptime	3927 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 	
js3250.dll + 0x1cec9 (0x6009cec9)
js3250.dll + 0x1d5e3 (0x6009d5e3)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d513 (0x6009d513)
firefox.exe + 0x1e2ea (0x0041e2ea)
js3250.dll + 0x2fffd (0x600afffd)
js3250.dll + 0x1d5e3 (0x6009d5e3)
js3250.dll + 0x1d513 (0x6009d513)
firefox.exe + 0x1e7d3 (0x0041e7d3)
js3250.dll + 0x1d5e3 (0x6009d5e3)
js3250.dll + 0x1d513 (0x6009d513)
firefox.exe + 0x1cfc5 (0x0041cfc5)
js3250.dll + 0x1d5e3 (0x6009d5e3)
js3250.dll + 0x1d513 (0x6009d513)
js3250.dll + 0x1d5e3 (0x6009d5e3)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d513 (0x6009d513)
firefox.exe + 0x1e2ea (0x0041e2ea)
js3250.dll + 0x2fffd (0x600afffd)
js3250.dll + 0x1d5e3 (0x6009d5e3)
js3250.dll + 0x1d513 (0x6009d513)
firefox.exe + 0x1434ec (0x005434ec)
firefox.exe + 0x145841 (0x00545841)
firefox.exe + 0x1e2de (0x0041e2de)
js3250.dll + 0x2fffd (0x600afffd)
js3250.dll + 0x1d5e3 (0x6009d5e3)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d640 (0x6009d640)
js3250.dll + 0x1d513 (0x6009d513)
js3250.dll + 0x1db0f (0x6009db0f)
js3250.dll + 0x1d93d (0x6009d93d)
firefox.exe + 0x4665ec (0x008665ec)
firefox.exe + 0x1013 (0x00401013)
kernel32.dll + 0x214c7 (0x77e614c7)

can you try crashing again with a newer build? (preferably not more than 1 day old)
I'll try to install the IME and to test it.
(Reporter)

Comment 8

13 years ago
Alright... Just one more time.
This is [Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051223 Firefox/1.6a1 ID:2005122305], it was automatically updated last night.
Now the incident ID is TB13398629Z.
dup of bug 237823 o bug 320256?

js_AllocStack  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsinterp.c, line 424]
nsXPCWrappedJSClass::CallMethod  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp, line 1170]
nsXPCWrappedJS::CallMethod  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/xpconnect/src/xpcwrappedjs.cpp, line 466]
SharedStub  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp, line 147]
nsEventListenerManager::HandleEventSubType  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/events/src/nsEventListenerManager.cpp, line 1684]
nsEventListenerManager::HandleEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/events/src/nsEventListenerManager.cpp, line 1791]
nsGlobalWindow::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp, line 1548]
nsGlobalWindow::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp, line 1440]
nsDocument::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/base/src/nsDocument.cpp, line 4218]
nsXULElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 1913]
nsXULElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 1910]
nsXULElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 1910]
nsXULElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 1910]
nsXULElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 1910]
nsXULElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 1910]
nsXULElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 1910]
nsXULElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 1910]
nsXULElement::HandleChromeEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/xul/content/src/nsXULElement.cpp, line 2590]
nsGlobalWindow::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp, line 1535]
nsGlobalWindow::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsGlobalWindow.cpp, line 1440]
nsDocument::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/base/src/nsDocument.cpp, line 4218]
nsGenericElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/base/src/nsGenericElement.cpp, line 2150]
nsGenericElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/base/src/nsGenericElement.cpp, line 2144]
nsGenericElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/base/src/nsGenericElement.cpp, line 2144]
nsGenericElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/base/src/nsGenericElement.cpp, line 2144]
nsGenericElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/base/src/nsGenericElement.cpp, line 2144]
nsGenericElement::HandleDOMEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/content/base/src/nsGenericElement.cpp, line 2144]
PresShell::HandleEventInternal  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/base/nsPresShell.cpp, line 6027]
PresShell::HandleEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/layout/base/nsPresShell.cpp, line 5863]
nsViewManager::HandleEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/view/src/nsViewManager.cpp, line 2545]
nsViewManager::DispatchEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/view/src/nsViewManager.cpp, line 2237]
HandleEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/view/src/nsView.cpp, line 176]
nsWindow::DispatchEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/widget/src/windows/nsWindow.cpp, line 1162]
nsWindow::DispatchMouseEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/widget/src/windows/nsWindow.cpp, line 6029]
ChildWindow::DispatchMouseEvent  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/widget/src/windows/nsWindow.cpp, line 6235]
nsWindow::WindowProc  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/widget/src/windows/nsWindow.cpp, line 1351]
USER32.dll + 0x8654 (0x77d18654)
USER32.dll + 0x8723 (0x77d18723)
USER32.dll + 0x8999 (0x77d18999)
USER32.dll + 0x8a12 (0x77d18a12)
nsAppStartup::Run  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 162]
main  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/browser/app/nsBrowserApp.cpp, line 61]
kernel32.dll + 0x214c7 (0x77e614c7)
QA Contact: amyy → i18n
Summary: Crash when using with Unispim Pinyin IME 3.0/4.0 → Crash when using with Unispim Pinyin IME 3.0/4.0 [@ js_AllocStack]
Keywords: stackwanted
Whiteboard: [needs retesting on Windows with Unispim Pinyin IME]
Keywords: inputmethod

Comment 10

6 years ago
Is this still reproducible/actual?

Comment 11

5 years ago
No response -> closing
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.