Guest

Preview Tool

Cisco Bug: CSCuj48450 - CoreAudio using cpu when J4M is idle

Last Modified

Aug 01, 2014

Products (1)

  • Cisco Jabber for Mac

Known Affected Releases

9.2(1)

Description (partial)

Issue requires investigation if this working as expected or a defect

Symptom:
CoreAudio using cpu when J4M is idle. The coreaudio process is using steady 4-7% cpu when Jabber is running. As soon as you close jabber it returns to 0 (and removes one coreaudio thread).

Conditions:
Steps:
1. Restarted Macbook Pro, no J4M app running and coreaudiod process has 4 threads and 0% cpu usage.
2. After launching J4M successfully, coreaudiod process still has 4 threads and 0% cpu usage.
3. Make a video call from J4M and coreaudiod process has 4/5 threads and ~2.2-2.5% cpu usage.
4. Ending the video call from J4M and coreaudiod process still has 5 threads and 2.4% cpu usage.
5. Quit J4M application and coreaudiod process has 4 threads and 0% cpu usage
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.