You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disposing objects from previous Python engine run does not seem to be a problem. There might have been an issue with that elsewhere, but it is not directly related.
Runtime.Py_Initialize();BorrowedReferencebuiltins=Runtime.PyEval_GetBuiltins();BorrowedReferenceiter=Runtime.PyDict_GetItemString(builtins,"iter");varownedIter=newNewReference(iter);// this basically does IncRefRuntime.Py_Finalize();Runtime.Py_Initialize();ownedIter.Dispose();// this basically does DecRefRuntime.Py_Finalize();// <- this blows up in PyGC_Collect -> validate_list
Environment
Details
Runtime
PyObject
s, keep them somewhereRuntime
Runtime
the second timeGC.Collect
andWaitForPendingFinalizers
Expected:
XDecref
should never be called on the handles inPyObject
s from step 2.Actual:
XDecref
is called on the handles inPyObject
s from step 2.I saw this happen even to .NET types reflected to Python like
System.MulticastDelegate
. Will soon open a PR with repro.The text was updated successfully, but these errors were encountered: