-
Notifications
You must be signed in to change notification settings - Fork 3.2k
macOS: speaker assertion persists after Herdr-spawned afplay exits; coreaudiod grows to ~5 GB #4595
Copy link
Copy link
Open
Labels
macosaffects macOS-specific behavioraffects macOS-specific behaviormaintainer-neededrequires maintainer judgment or maintainer-only reproductionrequires maintainer judgment or maintainer-only reproductionp2valid narrow or ordinary defect with limited impact or a practical workaroundvalid narrow or ordinary defect with limited impact or a practical workaroundperformanceCPU, memory, latency, throughput, or scaling behaviorCPU, memory, latency, throughput, or scaling behaviortriagedScreened; left open for investigation or maintainer judgment. Not proof of a bug or reproduction.Screened; left open for investigation or maintainer judgment. Not proof of a bug or reproduction.
Description
Activity
Metadata
Metadata
Assignees
Labels
macosaffects macOS-specific behavioraffects macOS-specific behaviormaintainer-neededrequires maintainer judgment or maintainer-only reproductionrequires maintainer judgment or maintainer-only reproductionp2valid narrow or ordinary defect with limited impact or a practical workaroundvalid narrow or ordinary defect with limited impact or a practical workaroundperformanceCPU, memory, latency, throughput, or scaling behaviorCPU, memory, latency, throughput, or scaling behaviortriagedScreened; left open for investigation or maintainer judgment. Not proof of a bug or reproduction.Screened; left open for investigation or maintainer judgment. Not proof of a bug or reproduction.
Is this a reproducible bug?
Current behavior
During normal use on September 24,
coreaudiodgrew to about 5 GB of memory footprint and reached 426% CPU. Read-only diagnostics found 117 retained built-in-speaker power assertions whose original creating processes had exited (including a PID that had subsequently been reused).One was tracked directly:
afplayPID 99583 was a child ofherdrPID 90740. Core Audio held anaudio-out BuiltInSpeakerDeviceassertion withCreated for PID: 99583. About 53 seconds later the player was gone, but that assertion remained.These are observations from an existing session, not proof that Herdr causes all the memory growth. Other audio apps were open. A sound-disabled control and reproduction on the latest release have not been completed.
Expected behavior
Audio resources associated with completed notification playback should be released; repeated notifications should not accompany accumulating stale audio assertions and sustained audio-daemon memory growth.
Reproduction
pmset -g assertionsandps -axo pid,ppid,etime,comm. Match a Herdr-launchedafplayPID to Core Audio'sCreated for PIDfield.coreaudiodremained abnormally busy.Impact
Severe laptop slowdown and repeated audio-daemon memory growth. I force-quit
coreaudiodafter collecting the above observations.Environment
herdr --version)