2

There's a core process (coreaudiod), that's crashing repeatedly. How can I find what's killing it? (i.e. is it another process?, is it a bug?, is RAM or CPU full?)

Improve this question
7
  • If there's a crash, see ~/Library/Logs/DiagnosticReports
    – anki
    Commented Jul 4, 2021 at 7:56
  • @anki Thanks to you, I've found 20 crash logs for coreaudiod. Can you post that as an answer?
    – Maytha8
    Commented Jul 4, 2021 at 8:56
  • The log says: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY. What does that mean?
    – Maytha8
    Commented Jul 4, 2021 at 8:59
  • The best you can do is look at the logs see stackoverflow.com/a/36361608/151019 but that does look like a bug or bad memory or you have a Kernal extention that is incorrect
    – mmmmmm
    Commented Jul 4, 2021 at 11:24
  • 1
    You can't diagnose a bad address to a released pointer as an end user. You need to find the extension that is causing it & remove it, update it, or ask the developer. I still think you've got 3rd party leftovers from your earlier question.
    – Tetsujin
    Commented Jul 4, 2021 at 11:26

1 Answer 1

Reset to default
7

Crash logs can be found in ~/Library/Logs/DiagnosticReports or in Console app.

The team that has access to the full code base for the app in question ( Apple) is best situated to make sense of these crash reports:

Depending on if the console app has some relevant errors logged and combined with how you are using the Mac when the process ends, you might have a chance to isolate what causes or contributes to this or have to reverse engineer or work with Apple to analyze these files.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .