Fix crash in QNN EP - ResetQnnLogLevel#22456
Merged
Conversation
HectorSVC
reviewed
Oct 17, 2024
ivberg
force-pushed
the
user/ivberg/ResetQnnLogLevel_CrashFish
branch
from
e8ecb53 to
840a671
Compare
HectorSVC
reviewed
Oct 22, 2024
Contributor
|
Is it possible to create some UTs to cover ETW feature? |
Contributor
Author
I do like the idea but need to see if possible? Ok if we do in another PR as timing need to get a fix in place ASAP |
HectorSVC
approved these changes
Oct 23, 2024
sophies927
added
release:1.20.0
triage:approved
apsonawane
pushed a commit
that referenced
this pull request
Oct 28, 2024
### Description Fix crash with extra checks ResetQnnLogLevel. From the dump it looks like during ETW callbacks, while the provider is stopping, we attempt to reset the QNN log level. While the QNN BackEndMgr (this) is alive logger_ is not valid ### Motivation and Context ORT should not crash
apsonawane
pushed a commit
that referenced
this pull request
Oct 28, 2024
### Description Fix crash with extra checks ResetQnnLogLevel. From the dump it looks like during ETW callbacks, while the provider is stopping, we attempt to reset the QNN log level. While the QNN BackEndMgr (this) is alive logger_ is not valid ### Motivation and Context ORT should not crash
apsonawane
pushed a commit
that referenced
this pull request
Oct 29, 2024
### Description Fix crash with extra checks ResetQnnLogLevel. From the dump it looks like during ETW callbacks, while the provider is stopping, we attempt to reset the QNN log level. While the QNN BackEndMgr (this) is alive logger_ is not valid ### Motivation and Context ORT should not crash
Contributor
|
This PR has been cherry-picked into the |
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
4 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.
Description
Fix crash with extra checks ResetQnnLogLevel.
From the dump it looks like during ETW callbacks, while the provider is stopping, we attempt to reset the QNN log level.
While the QNN BackEndMgr (this) is alive logger_ is not valid
Motivation and Context
ORT should not crash