Back to feed
Dev.to
Dev.to
7/18/2026
The Notification That Ate My MacBook: A Debugging Story

The Notification That Ate My MacBook: A Debugging Story

Short summary

A debugging narrative tracing a MacBook overheating issue to macOS's usernoted daemon pinned at 99% CPU. The root cause was a corrupted repeating notification with an unresolvable week-of-year calendar rule. Standard fixes like killing the process and removing calendar data all failed before a sample stack trace revealed the infinite loop in Foundation's calendar engine.

  • usernoted daemon consumed 99% CPU due to a corrupted notification date rule
  • Standard fixes (killall, calendar removal) all failed to resolve the spin
  • sample tool revealed infinite loop in Calendar week-of-year computation

Generated with AI, which can make mistakes.

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more