Hack patch for testing OTA update crash behavior #4942
Merged
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.
Why
There's a crash that's happening when
reloadAsync()
gets called byexpo-updates
. This is coming from attempting to destructure a null pointer, whenever removing all of theSharedObject
s inSharedObjectRegistry.clear()
.A little digging shows that the
deinit
block ofVideoPlayer
runs afterclear()
get's called. However, right nowclear()
callsdict.removeAll()
asynchronously inside of a separate queue from the main one. This is a small test to see if this helps to alievate the crashes. I don't consider this a production fix.Test Plan
Merge, let it build, and monitor for OTA crashes as we have been internally.