Summary
The Muesli home feed can become unresponsive when scrolling down through older transcription entries. macOS switches the pointer to the spinning beachball and the app stops responding.
Environment
- Muesli 0.8.1 (
com.muesli.app)
- macOS (installed app; Muesli requires macOS 14.2+)
- Home screen / transcription feed, with meeting transcripts visible
Steps to reproduce
- Open Muesli and stay on the home screen (the transcription feed).
- Scroll downward through older transcription entries, especially across long transcript content.
- Continue until reaching older entries.
Actual behavior
At some point the UI hangs: scrolling and other app interaction no longer respond, and the macOS spinning beachball cursor appears.
Expected behavior
The feed should remain responsive while older transcript entries are rendered and scrolled.
Notes
The issue appears intermittent. On one short local capture with two meeting transcripts, a single three-page scroll reached the oldest entries without hanging, so this report does not claim a deterministic reproduction yet. I could not capture the beachball itself without exposing the transcript text visible in the feed.
A likely investigation area is work performed synchronously while the home feed lays out or loads older, large transcription rows. A main-thread sample/spindump captured during the hang would help distinguish expensive text layout from a blocking database or sync path.
Summary
The Muesli home feed can become unresponsive when scrolling down through older transcription entries. macOS switches the pointer to the spinning beachball and the app stops responding.
Environment
com.muesli.app)Steps to reproduce
Actual behavior
At some point the UI hangs: scrolling and other app interaction no longer respond, and the macOS spinning beachball cursor appears.
Expected behavior
The feed should remain responsive while older transcript entries are rendered and scrolled.
Notes
The issue appears intermittent. On one short local capture with two meeting transcripts, a single three-page scroll reached the oldest entries without hanging, so this report does not claim a deterministic reproduction yet. I could not capture the beachball itself without exposing the transcript text visible in the feed.
A likely investigation area is work performed synchronously while the home feed lays out or loads older, large transcription rows. A main-thread sample/spindump captured during the hang would help distinguish expensive text layout from a blocking database or sync path.