Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Idle CPU stays at ~8% after the "Text wasn't inserted" card is shown once

Closed Beginner friendly
  • Is something wrong?
#1,217 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@nickbecker is already working on this.

Since Oct 22, 2026.

  • #1218 by @nickbecker — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
macos, swift
Domain
desktop, performance

Research direction

Start with TransientOverlayCountdownBar and DeliveryFailureOverlayController.hide(), named in the issue, and trace how the countdown view’s lifetime relates to the panel being ordered out. Reproduce by showing the delivery failure card and waiting for it to hide; confirm idle CPU returns to its earlier level afterward.

Written by the indexing model from the issue text.

Description

bug
Describe the bug

After the delivery-failure card appears and auto-hides, FluidVoice keeps using about 8% CPU while idle until it is relaunched. The card's countdown bar (TransientOverlayCountdownBar) uses TimelineView(.animation), which ticks at 30 Hz for as long as the view exists. DeliveryFailureOverlayController.hide() orders the panel out but keeps it, so the bar keeps redrawing in an invisible window.

Reproduction steps
  1. Run defaults write com.FluidApp.app FluidDebugRemoteToggleEnabled -bool true, relaunch FluidVoice, and wait a minute.
  2. Check idle CPU with top -pid $(pgrep -x FluidVoice): under 1%.
  3. Show the card: dictate with no text field focused, or post the distributed notification com.FluidApp.debug.showPasteFailure.
  4. Wait 10 seconds for the card to hide.
Expected behavior

Idle CPU returns to its earlier level.

Actual behavior

Idle CPU stays at a steady ~8% and never drops.

App Version

1.6.11 (28); same code on main at 1bf38dc8

macOS Version

27.0.1

Architecture

Apple Silicon

Logs or crash report
`sample` shows the main thread in a continuous `CA::Transaction::flush` / `NSHostingView.layout` loop.
An Instruments SwiftUI trace shows ~270 updates per second, all from `UpdateFilter<AnimationTimelineSchedule, GeometryReader<ZStack>>` inside `DeliveryFailureOverlayView`.
Screenshots or screen recording

No response

Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
1d 10h
Merged PRs (30d)
34

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from altic-dev/FluidVoice

All issues in altic-dev/FluidVoice

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.