Prevent renderer crash looping - #24152
Merged
Aragas merged 1 commit intoSep 9, 2026
Merged
Conversation
Prevent renderer crash looping
Aragas
approved these changes
Sep 9, 2026
Aragas
enabled auto-merge
September 9, 2026 13:35
Aragas
deleted the
cherry-pick/pr-24151-task-renderer-reload-fix-to-master
branch
September 9, 2026 13:50
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
1 participant
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.
Cherry-pick of #24151 into
master.The v2.6.2 telemetry has shown something pretty bad - there were 700 sessions that had Vortex looping with the renderer crashing.
Based on the code, the loop will never stop, which is definitely not good, since each crash goes to the telemetry. I'm adding a circuit breaker that will make Vortex exit if there's a loop detected.