Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

WASAPI: default-device activation fails with RPC_E_CHANGED_MODE after endpoint-notification callbacks put thread-pool threads into an STA

Aperta
  • Qualcosa non va?
#1,402 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@dannyward630 ci sta già lavorando.

Dal 24/10/2026.

  • #1413 di @dannyward630 — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
audio-video-rtc

Direzione di ricerca

Start in src/host/wasapi/stream.rs at DefaultDeviceNotificationImpl::OnDeviceRemoved and OnDeviceStateChanged, then follow get_current_default into current_default_endpoint in device.rs to where com_initialized() is called. Run the reproduction in the issue, which polls the default output device after thread-pool callbacks, and confirm RPC_E_CHANGED_MODE on the second open. Done means the default device opens after those callbacks run, without changing the calling thread's apartment.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

correctness host - wasapi platform - windows

cpal version: 0.18.2 (WASAPI host), Windows 11

What happens

After some time, opening the default input or output device fails for the rest of the process:

Failed to get audio client: Cannot change thread mode after it is set. (os error -2147417850)

(0x80010106 = RPC_E_CHANGED_MODE). Devices obtained from input_devices() / output_devices() (specific IMMDevices) keep working; only default_input_device() / default_output_device() fail. Only a restart of the process helps.

Cause
  1. DefaultDeviceNotificationImpl::OnDeviceRemoved and OnDeviceStateChanged (src/host/wasapi/stream.rs) call get_current_default → current_default_endpoint (device.rs), which calls com::com_initialized().
  2. These callbacks run on threads owned by Windows (MMDevAPI / thread pool), not on cpal's threads. com_initialized() calls CoInitializeEx(COINIT_APARTMENTTHREADED) there. On a pool thread that has no COM initialization of its own this succeeds, so the pool thread becomes an STA. The thread-local guard is only dropped when the thread exits, which pool threads normally do not, so the thread stays STA.
  3. For the default device, cpal activates via ActivateAudioInterfaceAsync(DEVINTERFACE_AUDIO_*) (activate_audio_interface_sync). When the process has a multithreaded apartment (any thread did CoInitializeEx(COINIT_MULTITHREADED), which many libraries do), the activation runs on the thread pool and fails with RPC_E_CHANGED_MODE on a pool thread that cpal turned into an STA.
Reproduction

Simulates step 1–2 by calling cpal's own path on pool threads (what the notification callbacks do):

use cpal::traits::{DeviceTrait, HostTrait};
use std::sync::atomic::{AtomicUsize, Ordering};
use windows::Win32::System::{Com::*, Threading::*};

static DONE: AtomicUsize = AtomicUsize::new(0);

unsafe extern "system" fn cb(_: PTP_CALLBACK_INSTANCE, _: *mut core::ffi::c_void) {
    let _ = cpal::default_host().default_output_device(); // -> current_default_endpoint -> com_initialized
    std::thread::sleep(std::time::Duration::from_millis(200));
    DONE.fetch_add(1, Ordering::SeqCst);
}

fn open() {
    std::thread::spawn(|| {
        let d = cpal::default_host().default_output_device().unwrap();
        println!("{:?}", d.supported_output_configs().map(|c| c.count()));
    })
    .join()
    .unwrap();
}

fn main() {
    // Some other thread in the MTA, as libraries commonly have.
    std::thread::spawn(|| {
        let _ = unsafe { CoInitializeEx(None, COINIT_MULTITHREADED) };
        loop { std::thread::park(); }
    });
    std::thread::sleep(std::time::Duration::from_millis(100));
    open(); // Ok(..)
    for _ in 0..64 {
        unsafe { TrySubmitThreadpoolCallback(Some(cb), None, None).unwrap() };
    }
    while DONE.load(Ordering::SeqCst) < 64 {
        std::thread::sleep(std::time::Duration::from_millis(10));
    }
    open(); // Err(Failed to get audio client: Cannot change thread mode after it is set. ...)
}

Observed: the first open() succeeds, every later one fails with RPC_E_CHANGED_MODE. Without the MTA thread both succeed. Calling a specific device's supported_output_configs() after the poisoning still succeeds.

Suggested fix

Code that runs on threads cpal does not own (the IMMNotificationClient callbacks, Drop of DefaultDeviceMonitor if it can run elsewhere) should not change that thread's apartment. For example, current_default_endpoint could skip com_initialized() when called from the callbacks, or join the MTA there (CoInitializeEx(COINIT_MULTITHREADED) / CoIncrementMTAUsage) instead of making the thread an STA. (Not verified: on which threads MMDevAPI invokes the callbacks; the reproduction above uses the default thread pool.)

Related: #1302 (enumerator bound to the first thread's apartment).

Lingua principale
Rust
Stelle
4k
Fork
554
Merge medio
2g 11h
PR unite (30g)
3

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di RustAudio/cpal

Tutte le issue di RustAudio/cpal

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.