Skip to content

Desktop app freezes with 100% CPU when typing with Microsoft Pinyin IME #36607

Closed as not planned

Description

@IsCibocaz

Description

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.

Environment:

OpenCode version:

main.log
renderer.log

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>)

Attempted workarounds (none resolved the issue):

--disable-gpu
--disable-direct-composition --disable-accelerated-2d-canvas
Clearing GPU cache, DawnGraphiteCache, DawnWebGPUCache directories
Additional notes:

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

Activity

  1. github-actions commented on Jul 13, 2026

    @github-actions
    Contributor

    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.

  2. github-actions commented on Sep 12, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions