Skip to content

Ensure IMEManager is fully initialized before processing messages - #227

Open
seer-by-sentry[bot] wants to merge 1 commit into
mainfrom
seer/fix-ime-early-message
Open

seer-by-sentry[bot] wants to merge 1 commit into
mainfrom
seer/fix-ime-early-message

Conversation

@seer-by-sentry

@seer-by-sentry seer-by-sentry Bot commented Jan 5, 2026

Copy link
Copy Markdown

Fixes CLIENT-1QZ. The issue was that: Access violation read 0x0 occurs when Windows UI/Audio components crash during IME context initialization due to an invalid state.

  • Introduced a global flag, gIMEInitialized, to track the completion of IMEManager initialization.
  • Updated WinMain::WndProc to only process IME messages via TheIMEManager->serviceIMEMessage if gIMEInitialized is true, preventing premature message handling.
  • Set gIMEInitialized = true in GameClient::init immediately following TheIMEManager->init().
  • Added a null check for m_candidateWindow in IMEManager::init before accessing its methods, guarding against potential crashes if the window script fails to load.

This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 8180239

Not quite right? Click here to continue debugging with Seer.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants