feat(music): crash breadcrumb for phase-attributed mobile crash reports - #60
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.