nextcloud / nextcloud/talk-desktop
**coreaudiod** process is using my battery on idle
Open
Nobody has claimed this yet.
bug
needs info
os: macOS 🍎
- Dominant language
- JavaScript
- Stars
- 525
- Forks
- 85
- Avg merge
- 8h 5m
- Merged PRs (30d)
- 35
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- start Talk Desktop on Mac (I am using M4 Max, Tahoe 26.5.1)
- have a audio+video conversation (not sure if this is strictly needed)
- close the conversation and leave the app idle
- coreaudiod process will keep eating battery (around 10%) while no audio is used
- restarting the app will fix it
Expected behaviour
When no audio is processed by the app I expect no battery drain by an audio process.
Actual behaviour
After an audio connection has been made, the daemon will keep active and consume cycles/power/battery.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Talk Desktop on macOS: make an audio/video conversation, close it, and leave the app idle while observing coreaudiod activity. Trace the audio connection lifecycle after the conversation closes; done means coreaudiod no longer consumes significant power when the app is idle without audio.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript
- Domain
- audio-video-rtc, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100