Skip to content

feat(music): crash breadcrumb for phase-attributed mobile crash reports - #60

Merged
Alex-Wengg merged 1 commit into
mainfrom
feat/crash-breadcrumb
Aug 24, 2026
Merged

feat(music): crash breadcrumb for phase-attributed mobile crash reports#60
Alex-Wengg merged 1 commit into
mainfrom
feat/crash-breadcrumb

Conversation

@Alex-Wengg

Copy link
Copy Markdown
Member

iPhone 17 still crashes repeatedly on /music after the C512 memory downshift (#58). iOS kills the tab silently, so we don't know WHICH phase dies — and the next fix differs completely by phase (window geometry vs. 3 GB DiT weight quantization). This persists the last progress stage in localStorage and reports it on the next visit after an unclean end. Zero effect on successful runs; breadcrumb closes on completion/failure/cancel.

iOS jetsam terminates the Safari tab with no error event, so repeated
iPhone crash reports carry no phase information. Progress updates now
persist a breadcrumb; a clean completion/failure/cancel closes it, and
the next visit reports 'previous attempt ended unexpectedly during:
<stage — detail>'. That single string decides the next fix: VAE/decode
stages are window-geometry territory, dit-denoise means the 3 GB
resident DiT weights and quantization.
@Alex-Wengg
Alex-Wengg merged commit 2fd0125 into main Aug 24, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant