Log messages when starting / ending freeze#14309
Merged
Merged
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
seanbudd
reviewed
Nov 2, 2022
seanbudd
approved these changes
Nov 2, 2022
This comment was marked as outdated.
This comment was marked as outdated.
Contributor
Author
|
Last system test failure: Unlikely to be related to this change. |
michaelDCurran
requested changes
Nov 2, 2022
michaelDCurran
left a comment
Member
There was a problem hiding this comment.
I'd like to see this change split into separate commits in the following order:
- Switch to using performance counters
- Add missing logging
- Refactor code
As much as I don't want to create extra work here, I'm finding it hard to follow all the changes and therefore can not be confident to give my assurance that the change looks correct. Especially also because the primary point of the pr was to add missing logging, not to necessarily refactor.
This comment was marked as outdated.
This comment was marked as outdated.
c3734e0 to
9eca5a2
Compare
Contributor
Author
|
@michaelDCurran The changes have been split. The refactor is composed of several aspects, I also made these separate commits. |
9eca5a2 to
44ee683
Compare
michaelDCurran
approved these changes
Nov 4, 2022
feerrenrut
added a commit
that referenced
this pull request
Nov 4, 2022
0721011 to
07419cb
Compare
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.
Link to issue number:
As per #14289 (comment)
Summary of the issue:
When NVDA freezes its behavior changes, this can break assumptions, and make inferring its behavior difficult.
The logs do not clearly indicate the start / end / level of a freeze.
Description of user facing changes
None
Description of development approach
Testing strategy:
Known issues with pull request:
Change log entries:
For Developers
Code Review Checklist: