[BUG] Windows 0.0.10: idle memory recycle is NOT invisible - console flashes + main window reopens fullscreen
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
- Ambito
- desktop
Direzione di ricerca
Start by tracing the memory-recycle flow described in the logs, from releasing the single-instance lock and starting the replacement through tray and main-window initialization. Reproduce with the app minimized to the tray and compare its visibility before and after recycling; done means a tray-hidden app stays hidden and no console flashes, while the reported memory growth is investigated.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Describe the bug
Per windows-v0.0.10 notes, the memory safety net "restarts itself when idle if its memory has grown past a threshold... The restart is invisible: it never happens while dictating or with the window open, and the replacement warms its models before you return."
On my machine the restart is very visible and disruptive:
- FluidVoice sits minimized in the tray.
- Randomly (mostly after ~5 min idle, sometimes while in use) a console window flashes, then the FluidVoice main window reopens fullscreen.
- I have to minimize/close it back to the tray every time.
Related: #917 (growth to ~3.9 GB, closed as stale). I already have the windows-runtime-parakeet-v0.4.0-fv1 fix (installed 2026-09-08, archive parakeet-v0.4.0-fv1-lib-win-cuda-x64.zip), yet recycles still fire.
Reproduction steps
- Install FluidVoice Windows 0.0.10, model "Blazing Fast - Multilingual" (parakeet.cpp/c-api, CUDA), launch at login (
--from-autostart). - Minimize/hide to tray, use normally for 1-5h.
- Leave idle ~5 min.
- Observe console flash + fullscreen main window reopen.
Expected behavior
Recycle stays in tray, no console window, no fullscreen restore - or at minimum preserves pre-recycle visibility (tray-hidden stays tray-hidden).
Actual behavior
fluidvoice.log (%APPDATA%\com.altic.fluidvoice.windows\fluidvoice.log) shows 3 recycles on 2026-09-21 (paths redacted):
Recycling process: reason=growth, private_mb=5732, baseline_mb=3548, uptime_s=18240, idle_s=305
Recycling process: reason=growth, private_mb=5918, baseline_mb=3289, uptime_s=11760, idle_s=319
Recycling process: reason=growth, private_mb=6083, baseline_mb=3289, uptime_s=4740, idle_s=306
Each followed by:
Released single-instance lock ahead of restart
Unloaded Fluid Intelligence runtime
FluidVoice 0.0.10 started on windows x86_64
Previous session ended without a clean exit while idle
Starting Fluid Intelligence startup warmup
tray icon created / Recording overlay window created (380x137)
Recycle replacement confirmed; exiting old process
Recycle floor updated: private_mb=3741 / 5445 / 4142
Post-recycle floor itself climbs (3289 -> 5445 MB), and the 3rd recycle fired after only ~79 min uptime - so growth persists despite fv1, and the "invisible" restart is not invisible.
Side evidence of focus disruption on a normal dictation:
Insertion target refocus ... before="System tray overflow window", after="OpenCode"
App Version
Windows 0.0.10 (GUI subsystem), runtime parakeet-v0.4.0/cuda (fv1, installed 2026-09-08).
Environment
- Windows 11 x64, NVIDIA GPU, CUDA enabled (parakeet CUDA + llama CUDA)
- Model: Parakeet TDT 0.6b v3 ("Blazing Fast - Multilingual")
launch_at_login: true, autostart entryfluidvoice.exe --from-autostart
Workaround
Keeping the main window open seems to suppress it (matches "never ... with the window open"), then restarting manually when convenient. Not ideal.
Request
- Make recycle preserve tray-hidden state: spawn replacement hidden, don't restore the main window unless it was visible pre-recycle.
- Re-check growth: floor rising to ~5.4 GB post-fv1 suggests a residual leak or an over-sensitive threshold.
- Consider a setting to disable/schedule the safety-net restart.
No personal data included intentionally; happy to provide redacted logs on request.
- Lingua principale
- Swift
- Stelle
- 11.9k
- Fork
- 863
- Merge medio
- 1g 13h
- 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
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di altic-dev/FluidVoice
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
altic-dev/FluidVoice#1149 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 40/100
altic-dev/FluidVoice#1148 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 22/100
altic-dev/FluidVoice#1147 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 Mezza giornata Idoneità per principianti 55/100
altic-dev/FluidVoice#1146 ·
I maintainer di solito rispondono entro 1 giorno
-
[BUG] transcripted text sometimes disappears after 2nd press of the shortcut to end recordingApertabug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
altic-dev/FluidVoice#1144 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di altic-dev/FluidVoice
Issue simili
-
builtin-port enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
cmlarsen/writemorebetter#235 ·
I maintainer di solito rispondono entro 1 giorno
-
bug-pending-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
NativeScript/NativeScript#11525 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
callstack/agent-device#3627 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno