You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Desktop app freezes with 100% CPU when typing with Microsoft Pinyin IME #36607
When typing Chinese characters using Microsoft Pinyin IME (ChsIME.exe) in the OpenCode desktop app, all CPU logical processors immediately spike to 100%, the input method and the app UI freeze, and after typing for a while the app becomes completely unresponsive.
OS: Windows (ConsoleHost)
CPU: 12th Gen Intel Core i5-12600KF (10 cores, 16 logical processors)
IME: Microsoft Pinyin IME (ChsIME.exe)
Plugins
none
OpenCode version
1.17.18 (Electron 42.3.3)
Steps to reproduce
Steps to reproduce:
Launch OpenCode desktop app
Switch to Microsoft Pinyin IME
Start typing Chinese characters - CPU immediately maxes out and the UI freezes
Logs: The renderer log is flooded with repeated errors:
ResizeObserver loop completed with unsent notifications.
(See renderer.log in %APPDATA%\ai.opencode.desktop\logs<latest>)
The CLI version of OpenCode does not have this problem
This appears to be a Chromium/Electron compositor issue triggered by the IME candidate window causing a ResizeObserver feedback loop
Screenshot and/or share link
N/A - unable to screenshot while app is frozen
Operating System
Windows 10 Pro for Workstations 22H2 x64 (19045.6332)
Terminal
N/A - using the OpenCode desktop app, not a terminal emulator
Your issue specifically identifies the Microsoft Pinyin IME candidate window as the trigger for the ResizeObserver loop — that context is useful and may help narrow down the fix, so please keep this open if the above issues don't fully cover the IME-specific trigger.
Activity
github-actions commentedon Jul 13, 2026
This issue might be a duplicate of existing issues. Please check:
Your issue specifically identifies the Microsoft Pinyin IME candidate window as the trigger for the ResizeObserver loop — that context is useful and may help narrow down the fix, so please keep this open if the above issues don't fully cover the IME-specific trigger.
github-actions commentedon Sep 12, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.