Open Bug 1925184 Opened 19 days ago Updated 14 days ago

Crash in [@ googleinput_hi.ime] with Google IME version 1.0.4.0

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

Unspecified
Windows 11
defect

Tracking

()

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/bfb3c556-d158-400b-9753-f49950241017

Reason:

Unhandled C++ Exception

Top 10 frames:

0  KERNELBASE.dll  RaiseException
1  GOOGLEINPUT_HI.IME  GOOGLEINPUT_HI.IME@0x1270bf
2  GOOGLEINPUT_HI.IME  GOOGLEINPUT_HI.IME@0x16921f
3  GOOGLEINPUT_HI.IME  GOOGLEINPUT_HI.IME@0x678f
4  ntdll.dll  RcConsolidateFrames
5  GOOGLEINPUT_HI.IME  GOOGLEINPUT_HI.IME@0x677a
6  GOOGLEINPUT_HI.IME  GOOGLEINPUT_HI.IME@0x123b52
7  GOOGLEINPUT_HI.IME  GOOGLEINPUT_HI.IME@0x14117f
8  GOOGLEINPUT_HI.IME  GOOGLEINPUT_HI.IME@0x674f
9  GOOGLEINPUT_HI.IME  GOOGLEINPUT_HI.IME@0x12703d

These appear to be crashes with a positively ancient version of Google IME (10+ years old). The stack is terrible and I don't know if we can do anything about it, but I'm filing this to track it.

It seems that it's discontinued and Google Input Tools replaced the products. However, I don't find the download page of its Windows version. So it seems that the users may need to keep using the old version.

On the other hand, Text Services Framework (TSF) on Windows which is API for both IME and apps has been changed a lot. Therefore, even as far as I know, some Japanese IMEs stopped working too. So, it might be impossible to support such old IMEs anymore.

You need to log in before you can comment on or make changes to this bug.