Open
Conversation
Contributor
Author
|
An alternative solution suggested by Opus would be to add
The solution to that is // SurfaceDestroyed fires before OnDestroy and unsubscribes the view from the
// ChoreographerTimer, stopping the render thread. Disposing the root triggers
// HandleClosed ? Renderer.Dispose ? SyncDisposeCompositionTarget, which needs
// the render thread alive to process the batch. Temporarily re-subscribe so the
// choreographer keeps firing while the synchronous wait completes.
IDisposable? tempSubscription = null;
if (AndroidPlatform.Timer is { } timer)
tempSubscription = timer.SubscribeView(this);
tempSubscription?.Dispose();in |
|
You can test this PR using the following package version. |
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.
What does the pull request do?
Fixes #20883.
What is the current behavior?
Crash on back pressed/minimize.
What is the updated/expected behavior with this PR?
No crash.
How was the solution implemented (if it's not obvious)?
_viewisn't set tonullonTopLevelImpldispose. Since the render call that causes the crash only accesses .NET resources inAvaloniaView, this should be fine. On the flip side, the view's Java handle might not be released immediately when the main activity is destroyed.Checklist
Breaking changes
No.