| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Great catch, thank you very much! |
Sorry, something went wrong.
There was a problem hiding this comment.
Please, revert whitespace changes (wrong line breaks?)
Sorry, something went wrong.
… the list before reaching end.
|
I amended the last commit with 'right' line breaks. Did it work propertly? Sorry I'm not used to this 'push request' workflow. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
System.AccessViolationException occurs when iteration quits in the middle of list before reaching the end.
Environment
Reproduce the problem
I'm trying to pass a list from python to .NET method via List Codec.
Conversion(decode) is successful and mylist is wrapped by ListWrapper.
.NET code receives the list like this.
Using Enumerator of mylist, if enumerated to the end of the list, nothing bad happens.
However if iteration didn't go to the end of the list, AccessViolationException is thrown.
This case happens in the following code:
similarly
The following code doesn't throw exception becuase it always iterates to the end of the list.
Exception occurs because PyIter(ator) object is Dispose(d) outside of GIL protection only when iteration ends before reaching the end ( before MoveNext() returns null ).
In such a case, code process just slips out of GIL enclosure as the nature of C# scope and yield return and break.
solution for now
original code is like this:
using var _ = iterObject; above the while loop is the problematic line.
Before iteration reaches the end, the executing process is somewhere out of the using scope.
When c# caller process stops iteration(Enumeration) for some reason, c# suddely calls
using var _ = iterObject; 's closing process which is iterObject.Dispose().
But here iterObject is not inside of GIL() protection. This is why exception occurs.
Solution is to make sure iterObject.Dispose() is always inside of GIL protection and
always executed whatever the caller process abandons the enumeration in the middle.
My suggestion is to use try catch pattern. Without catching any exception it may look odd. But this is one solution to make sure the execution of Dispose and GIL scope surrounding always.