Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

cpal + dioxus_desktop: eats memory and dies

Abierto
#782 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
32/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
rust
Área
backend

Línea de trabajo

Start by reproducing the memory spike with the minimal CPAL stream and Dioxus Desktop launch shown in the issue, then compare each program running alone. The payload names no repository files or tests and does not identify which library causes the interaction, so debugging will require tracing both libraries' startup paths. Done means the combined program opens its window without unbounded memory use while the audio stream runs.

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

Descripción

With latest versions:

cpal = { version = "0.15.2", features=["jack"] }

dioxus = "0.3.2"
dioxus-ssr = "0.3.0"
dioxus-desktop = "0.3.0"

Consider this minimal code:

use cpal::traits::{DeviceTrait, HostTrait, StreamTrait};
use cpal::{BufferSize, Device, Stream, StreamConfig, SupportedBufferSize};
use std::cmp::max;

fn main() {
    let _stream = start_cpal();

    loop {}
}

fn start_cpal() -> Stream {
    let device = get_device();
    let config = get_config(&device);

    let stream = device
        .build_output_stream(
            &config,
            move |_: &mut [f32], _: &cpal::OutputCallbackInfo| {},
            move |_| {},
            None,
        )
        .unwrap();

    stream.play().unwrap();
    stream
}

fn get_device() -> Device {
    let host_id = cpal::available_hosts()[0];
    let host = cpal::host_from_id(host_id).unwrap();

    host.default_output_device().unwrap()
}

fn get_config(device: &Device) -> StreamConfig {
    let mut supported_configs_range = device.supported_output_configs().unwrap();
    let supported_config = supported_configs_range
        .next()
        .unwrap()
        .with_max_sample_rate();

    let mut config = supported_config.config();
    config.buffer_size = BufferSize::Fixed(get_some_buffer_size(supported_config.buffer_size()));

    config
}

fn get_some_buffer_size(spec: &SupportedBufferSize) -> u32 {
    match spec {
        SupportedBufferSize::Range { min, .. } => max(*min, 64),
        SupportedBufferSize::Unknown => 64,
    }
}

It works as expected (program runs; nothing happens). I also get sound if I put something in the data callback.

Enter dioxus desktop:

fn main() {
    let _stream = start_cpal();

    dioxus_desktop::launch(app);
}

use dioxus::prelude::*;
fn app(cx: Scope) -> Element {
    cx.render(rsx!("lol"))
}
// .. same code as before

Expected result: cpal still works; Dioxus window shows up.

Actual result: program eats all the memory and the OS kills it. No window shows up.

Resource monitor screenshot: spike in memory usage

The start of the spike is where I run the program. It falls back down after a few seconds when the process is killed.

The issue is not with Dioxus alone, because this program works as expected:

fn main() {
    dioxus_desktop::launch(app);
}

The problem only occurs when I use cpal and Dioxus in the same program.

I don't know if this is an issue with Dioxus or cpal, and I have no idea where to begin debugging this. Any ideas please?

I'm on Ubuntu 22.04.2 LTS. Lemme know if you need any other details. Thank you!!

Lenguaje dominante
Rust
Estrellas
4k
Forks
554
Merge medio
3 d 3 h
PR fusionados (30 d)
4

Preparar el entorno

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 RustAudio/cpal

Todos los issues de RustAudio/cpal

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.