Fix manager screen tick history crash - #589
Draft
TeamDman wants to merge 1 commit into
Draft
Conversation
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.
Fixes #535
Summary
Opening the manager screen before any program has produced tick-time samples can crash while rendering the performance graph. The history contains null entries until samples exist.
This change treats null samples as zero-duration values for peak calculation, graph plotting, and hover text, preserving normal graph behavior once timing data arrives. It also adds a changelog entry.
Validation
sfm-propagate-changes.exe run compile --branch agent/fix-535-manager-screen-null --wait-for-build-locksfm-propagate-changes.exe test run --branch agent/fix-535-manager-screen-null --wait-for-build-lock