Native crash (SIGSEGV in getSuggestionsNative) when typing with a multilingual secondary language
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with DictionaryFacilitatorImpl.getSuggestionResults(), where secondary-dictionary queries run in scope.launch and are awaited for 120 ms, then BinaryDictionary.getSuggestions(), where only getTraverseSession() is synchronized and the native call is not. The work is to confirm that overlapping queries share one DicTraverseSession and then make access to that session safe; the reporter already has a candidate fix. Done means no SIGSEGV under overlapping queries, which needs a device or a concurrency reproduction.
由索引模型根据 Issue 内容生成。
描述
Describe the bug
With a secondary language added via Multilingual typing (German + English (US), both main dictionaries installed), the keyboard process sometimes crashes in native code (SIGSEGV, null pointer dereference in libjni_latinime.so). For us it happened right after tapping the clipboard suggestion and when typing fast.
Backtrace (shortened):
F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x11 in tid 10828 (DefaultDispatch)
F DEBUG : Cause: null pointer dereference
F DEBUG : #00..#04 libjni_latinime.so
F DEBUG : #11 com.android.inputmethod.latin.BinaryDictionary.access$getSuggestionsNative
F DEBUG : #24 com.android.inputmethod.latin.BinaryDictionary.getSuggestions
F DEBUG : #30 helium314.keyboard.latin.dictionary.ReadOnlyBinaryDictionary.getSuggestions
F DEBUG : #35 helium314.keyboard.latin.dictionary.DictionaryCollection.getSuggestions
F DEBUG : #38 helium314.keyboard.latin.DictionaryFacilitatorImpl.getSuggestions
F DEBUG : #49 helium314.keyboard.latin.DictionaryFacilitatorImpl$getSuggestionResults$1.invokeSuspend
F DEBUG : #53 kotlinx.coroutines.DispatchedTask.run
Cause (from reading the code)
DictionaryFacilitatorImpl.getSuggestionResults() queries the secondary dictionary groups in scope.launch {} on a background thread and waits for them only up to await(120, TimeUnit.MILLISECONDS) (reduced from 500 ms in 05023da). If a query takes longer, the next keystroke starts a new query on the same dictionary while the previous one is still running.
Both queries use the same DicTraverseSession (same session id). Its Java buffers (mInputCodePoints, mPrevWordCodePointArrays, ...) and the native session are shared. BinaryDictionary.getSuggestions() only synchronizes the session lookup in getTraverseSession(), not the native call, so two threads can run getSuggestionsNative() on the same native session at the same time.
Fix that works for us
Hold a lock on the session for the whole query in BinaryDictionary.getSuggestions():
val session = getTraverseSession(sessionId)
synchronized(session) {
// fill the session buffers, call getSuggestionsNative(..., session.getSession(), ...), read the results
}
(and pass session.getSession() instead of calling getTraverseSession(sessionId) a second time). We haven't seen the crash since. I can send a PR once we've tested it a bit longer.
To Reproduce
- Languages & Layouts → German → Multilingual typing → add English (US). Install the main dictionaries for both.
- Type fast, or copy some text and tap the clipboard suggestion right away.
- Occasionally the keyboard crashes and restarts. It depends on timing, so it doesn't happen every time.
Expected behavior
No crash.
App version & Flavor
Found in GlassType, my fork based on LeanType 4.3.0 (d634e26), standard flavor. BinaryDictionary.getSuggestions() is unchanged in current main (0e673e1), and getSuggestionResults() now waits even shorter (120 ms).
Device Info
- Model: Samsung Galaxy S23 Ultra (SM-S918B)
- OS version: Android 17
- 主要语言
- Kotlin
- 星标
- 1k
- 派生
- 59
- 平均合并
- 14 小时 9 分钟
- 30 天内合并 PR
- 56
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
LeanBitLab/LeanType 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
LeanBitLab/LeanType#760 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 62/100
LeanBitLab/LeanType#763 ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 62/100
LeanBitLab/LeanType#762 ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 70/100
LeanBitLab/LeanType#761 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 30/100
LeanBitLab/LeanType#757 · 4 条评论 ·
维护者通常 1 天内回复
查看 LeanBitLab/LeanType 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
liberation-data/drivine4j#547 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
ccch1mneyyy/dsh-Go#381 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
wangzan101/Mika#227 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 72/100
theopenconversationkit/tock#2136 ·
维护者通常 1 天内回复
-
App asks for diameter for emergency=hydrant + water_source=groundwater. But should probably not.未关闭feedback required
难度 2/5 1-3 小时 新手友好度 62/100
streetcomplete/StreetComplete#7354 · 1 条评论 ·
维护者通常 1 天内回复