Closed Bug 1512165 Opened Last year Closed 11 months ago
Crash in sogoutsf
This bug was filed from the Socorro interface and is report bp-0a35b037-9c93-4a3b-b632-179ec0181124. ============================================================= Top 10 frames of crashing thread: 0 sogoutsf.ime sogoutsf.ime@0x474a0 1 sogoutsf.ime sogoutsf.ime@0x47959 2 sogoutsf.ime sogoutsf.ime@0x47346 3 msctf.dll CInputContext::_DoEditSession 4 msctf.dll CInputContext::_EditSessionQiCallback 5 msctf.dll CInputContext::_EmptyLockQueue 6 msctf.dll CACPWrap::OnLockGranted 7 xul.dll mozilla::widget::TSFTextStore::RequestLock widget/windows/TSFTextStore.cpp:2305 8 msctf.dll CACPWrap::RequestLock 9 msctf.dll CInputContext::_QueueItem ============================================================= crash reports like this one with the Sogou Pinyin input method have become more common during the 65 nightly cycle. they are all from installations on windows 10 with a11y active.
Looks like that at least the stack in comment 0 is caused by internal bug of Sogou Pinyin because we grabs necessary objects with local variables correctly when calling ITfKeystrokeMgr::KeyDown() and ITextStoreACPSink::OnLockGranted() but Sogou Pinyin references nullptr. I guess that Sogou reads web content or something with a11y API. A Japanese 3rd party IME, ATOK, also does use a11y API to read content in focused editor to improve suggestion from IME. But perhaps, a11y is not related to this crash. Last update of Sogou Pinyin is 2018-12-5. So, it must be new regression of them. (Or, we are just victim of new race condition between treads. We experienced such issue of Japanese Microsoft IME in this Q1 and Q2.)
Do we have contacts with Sogou?
looking at the crashing graph for beta it's only correlating with the rollout of 65 to the beta population, so i think it's likely something in our codebase that's triggering the crashes more often since 65...
We didn't touch TSFTextStore in 65 cycle...
are these crashes reproducible while using Sogou Pinyin and if so, would it be possible to come up with a regression range for the issue? thank you
sorry for the late reply. I am trying to reproduce this question, but I don't see it clearly related to 65beta? There is currently no user feedback on this issue. I have previously contacted the Sogou input method because of other problems. They used a11y's screen reading function to analyze the content of the web page and input environment to complete. I'm not sure if this is relevant, but this feature should be used very early.
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.