_platform_strlen

[sentry]

Sentry Issue: NEXU-DESKTOP-PROD-16

EXC_BAD_ACCESS / KERN_INVALID_ADDRESS / 0x0: Fatal Error: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS / 0x0
  ?, in _platform_strlen
  ?
  ?, in strdup
  ?
  ?
...
(5 additional frame(s) were not displayed)

This issue was automatically created by Sentry via Send new issues to slack and github

[lefarcen]

This looks like an opaque native macOS crash rather than an app-level JS exception: the captured stack is EXC_BAD_ACCESS / KERN_INVALID_ADDRESS / 0x0 with _platform_strlen → strdup, but the GitHub payload does not include enough frames to identify the owning Nexu call path yet.

I checked the nearby Sentry-created crash issues and the desktop crash-reporting path; keeping this as bug + sentry is the right initial triage. The next useful evidence is the Sentry event's release/dist, OS + arch, breadcrumbs, and full native thread list/minidump. If this repeats on the same release, we should prioritize symbolication / Crashpad details before assigning an implementation fix.