ByteBufferAsyncProcessor: prevent deadlocks on corrupted state exceptions#189
Merged
ByteBufferAsyncProcessor: prevent deadlocks on corrupted state exceptions#189
Conversation
ForNeVeR
force-pushed
the
net211.im/safe-logger
branch
from
f3bb6e8 to
6be05b1
Compare
…ions It turns out that some of our code works under [HandleProcessCorruptedStateExceptions] attribute on .NET Framework. This attribute allows the process to proceed execution even in case of memory access violation, but will only execute catch and finally blocks in direct methods marked with the attribute. So, if ByteBufferAsyncProcessor.Put is called from such method, and then an exception occurs inside of the lock block, the lock will be abandoned in a locked state. This could lead to deadlocks that are hard to detect. Provided we don't want to change the behavior of all the external code right now, the safest action we could take is to guard the path leading to our logger with the same attribute. It will at least help to preserve the logger functionality even in case of corrupted state exception, which should be helpful.
ForNeVeR
force-pushed
the
net211.im/safe-logger
branch
from
6be05b1 to
55cf06c
Compare
ulex
approved these changes
Dec 19, 2020
sergeyQx
reviewed
Dec 21, 2020
|
|
||
|
|
||
| #if !NET35 | ||
| [System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptions] // to force myLock to be unlocked even in case of corrupted state exception |
Contributor
There was a problem hiding this comment.
I would have also added logging of the exception
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
3 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.
It turns out that some of our code works under
HandleProcessCorruptedStateExceptionsattribute on .NET Framework. This attribute allows the process to proceed execution even in case of memory access violation, but will only executecatchandfinallyblocks (including the implicitly generatedfinallyin case of alockblock) in methods directly marked with the attribute.So, if
ByteBufferAsyncProcessor.Putis called from such method, and then a corrupted state exception occurs inside of thelockblock, the lock will be abandoned in a locked state. This could lead to deadlocks that are hard to detect.Provided we don't want to change the behavior of all the external code right now, the safest action we could take is to guard the path leading to our logger with the same attribute. It will at least help to preserve the logger functionality even in case of corrupted state exception, which should be helpful.