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

[BUG] Windows 0.0.9: activation latency grows from 220 ms to 6+ s over multi-day uptime (memory grows to ~3.9 GB); restart fully resets

Aperta
  • Qualcosa non va?
#917 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
swift
Ambito
performance

Direzione di ricerca

Start by tracing the recorder startup and overlay-show paths corresponding to start_request_to_recorder_ready_ms and start_request_to_recording_overlay_visible_ms in the reported fluidvoice.log excerpt. Compare those timings and memory use after a fresh launch and after extended uptime using the listed Windows 0.0.9 reproduction steps. Done means identifying and fixing the cause so activation latency and memory remain stable during multi-day use.

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

Descrizione

bug keep-open windows
Describe the bug

FluidVoice Windows 0.0.9 degrades over multi-day uptime. After ~4 days running continuously, the process working set had grown to 3.9 GB (private bytes ~3.0 GB) and every dictation activation stalled for seconds before recording started. Because the recording overlay waits on the recorder, the overlay also appears seconds late (or seemingly not at all if the user releases the hold-mode shortcut first). A restart of the app fully resets both memory and latency, with no other changes to the system.

Reproduction steps
  1. Install FluidVoice Windows 0.0.9, Parakeet v3 q8 model ("Blazing Fast - Multilingual", parakeet.cpp/c-api, CPU), hold activation mode, Ctrl+Win shortcut.
  2. Leave the app running for several days of normal daily dictation use (no reboots).
  3. Press the shortcut and observe the delay before the overlay/recording starts.
  4. Restart the app and repeat — latency returns to normal immediately.
Expected behavior

Activation latency stays roughly constant regardless of app uptime; memory stays near the fresh-launch footprint plus the loaded model.

Actual behavior

App-reported dictation_performance metrics from fluidvoice.log on the same machine, same version, same model:

Metric Fresh launch After ~4 days uptime
start_request_to_recorder_ready_ms 220 6,025
start_request_to_recording_overlay_visible_ms 4 4,458
transcribe_ms 231 (4.4 s audio) 1,079 (20.7 s audio)
Process working set ~43 MB at launch (before model load) 3,959 MB

Transcription itself stays fast; the regression is entirely in activation/recorder startup.

Log excerpt from the degraded state — note the process logs nothing at all for 4.4 s between the overlay show event and the overlay becoming visible (looks like an internal stall, not an audio-device wait):

14:16:32.820 [INFO] Starting recording: device=System default, max_seconds=unlimited, ...
14:16:32.820 [INFO] Overlay show requested: state=recording
14:16:32.821 [INFO] Overlay positioned: x=3330.0, y=1216.0
14:16:32.821 [INFO] Overlay show-overlay event emitted: state=recording
        <-- no log output for 4.4 seconds -->
14:16:37.277 [INFO] Overlay window shown without activation
14:16:37.278 [INFO] Overlay visible: state=recording, show_ms=4457
App Version

Windows 0.0.9 (windows-v0.0.9)

Environment
  • Windows 11 Pro 10.0.26200, x64, 128 GB RAM (system otherwise healthy when measured: 69 GB free RAM, ~25% CPU)
  • Model: Parakeet TDT 0.6b v3 q8 GGUF, CPU inference
  • Activation mode: hold; AI enhancement globally enabled but not used in these dictations (fi_requested: false)
Workaround

A scheduled nightly restart of the app fully mitigates it.

(Reported with the help of Claude, which gathered the metrics from fluidvoice.log on the affected machine.)

Lingua principale
Swift
Stelle
11.9k
Fork
863
Merge medio
1g 12h
PR unite (30g)
27

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 altic-dev/FluidVoice

Tutte le issue di altic-dev/FluidVoice

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.