Perfomance: avoid stack trace allocation when cancelling RectManager per-frame callbacks - #3411
Merged
Merged
Conversation
…per-frame callbacks
Konstantin (terrakok)
requested review from
Ivan Matkov (MatkovIvan) and
Oleksandr Karpovich (eymar)
September 10, 2026 18:43
Oleksandr Karpovich (eymar)
approved these changes
Sep 10, 2026
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
2 participants
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.
When coroutines are being canceled, usually a CancellationException is created. And it means a new call stack of the error are being collected. It takes time.
My fix avoid that by using a prepared error instance. It is safe, because it is internal process and there is no need to provide a real call side for users.
Release Notes
Fixes - Multiple Platforms