Vivaldi (Chromium-based browsers) freeze on macOS 26 Tahoe due to IMKInputSession deadlock triggered by input source switching

Abierto
  • ¿Algo no está bien?
#92 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
macos, swift
Área
desktop

Línea de trabajo

Start from where Input Source Pro calls TISSelectInputSource when an app gains focus (the focus-observation/switching code in the Swift app), since that call is what triggers IMKInputSession activate inside Vivaldi. Investigate whether the switch can be deferred, throttled, or performed off the target app's activation path so Chromium's firstRectForCharacterRange query cannot race it. Done means a documented mitigation that avoids the XPC deadlock on macOS Tahoe, verifiable by reproducing the Cmd+T navigation freeze with the fix applied. The issue has no comments, no linked PR, and is 194 days old, so confirm maintainers still want it handled before investing.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Steps to Reproduce
  1. Have Input Source Pro configured to automatically switch input source when focusing Vivaldi (e.g., switch to Chinese input when Vivaldi becomes active)
  2. Open Vivaldi
  3. Open a new tab (Cmd+T)
  4. Type a URL in the address bar (e.g., claude.ai or google.com) and press Enter
  5. Observe the browser becoming completely unresponsive for 15–30 seconds before recovering

The freeze is reliably reproducible on new tab navigation and hit-or-miss on subsequent navigations within the same tab.

Expected Behavior

Input Source Pro switches the input method when Vivaldi gains focus without causing any freeze or unresponsiveness in the browser.

Actual Behavior

Vivaldi's main thread deadlocks for 15–30 seconds. The browser is completely unresponsive — no scrolling, clicking, or typing possible. It eventually recovers on its own. Quitting Input Source Pro completely eliminates the freeze.

A spindump captured during the freeze shows Vivaldi's main thread (CrBrowserMain) blocked in IMKInputSession_Modern activate → invocationAwaitXPCReply → HIRunLoopSemaphore wait → psynch_cvwait, while simultaneously Chromium's text input bridge is blocked in firstRectForCharacterRange → psynch_cvwait — a classic XPC deadlock between the IME activation triggered by Input Source Pro and Chromium's concurrent cursor position query.

Relevant portion of spindump stack trace:

Thread 0x4b4df7  DispatchQueue "com.apple.main-thread"  CrBrowserMain  1934 samples

-[NSTextInputContext handleTSMEvent:completionHandler:]
  → TUIRectForCharacterRange
    → -[NSTextInputContext firstRectForCharacterRange:completionHandler:]
      → ChromeMain → psynch_cvwait   ← BLOCKED

CallMyActivateTSMDocument
  → IMKInputSession_Modern activate
    → IMKInputSessionXPCInvocation_Modern invocationAwaitXPCReply
      → HIRunLoopSemaphore wait
        → __CONSIDER_WHO_REQUESTED_THIS_WAIT_BEFORE_SENDING_BUG_TO_HISERVICES__
          → psynch_cvwait   ← BLOCKED

Both call chains are blocked simultaneously waiting on each other, causing a full deadlock.

After quitting Input Source Pro and capturing a second spindump under identical conditions, the main thread shows a completely healthy idle state (mach_msg2_trap in normal event loop wait) with no IMKInputSession activity and no freeze.

Environment
Field Value
Input Source Pro Version 2.9.0 (605)
macOS Version macOS 26.3.1 (Build 25D771280a) — Tahoe beta
Affected Application Vivaldi 7.9.3970.45 (Chromium-based). Likely affects all Chromium-based browsers (Chrome, Edge, Arc, etc.) as the root cause is in Chromium's NSTextInputContext bridge, not Vivaldi specifically
Relevant Input Sources U.S. English + Chinese Simplified (Pinyin) — Input Source Pro configured to switch to Chinese when Vivaldi is focused
Additional Context

The root cause appears to be a race condition introduced or worsened in macOS Tahoe's TextInputUIMacHelper framework. When Input Source Pro calls TISSelectInputSource on app focus, it triggers IMKInputSession activate on Vivaldi's main thread. Simultaneously, Chromium's text input bridge attempts to call firstRectForCharacterRange to query cursor position from the same IME session. Both calls block on XPC waiting for the other to complete, resulting in a deadlock.

The issue does not affect:

  • Safari — uses native AppKit/WebKit text input and handles IME activation differently
  • Firefox-based browsers (e.g., Zen) — use a completely different text input stack
Lenguaje dominante
Swift
Estrellas
3.6k
Forks
144
Merge medio
14 h 21 min
PR fusionados (30 d)
7

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de runjuu/InputSourcePro

Todos los issues de runjuu/InputSourcePro

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.