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
{{ message }}
This repository has been archived by the owner on Aug 5, 2021. It is now read-only.
This bug manifested itself as a failure of the unit test PyObjectTest.testDictCopy(). It can also be triggered by the following minimal snippet (Python 3.8, 64-bit Ubuntu Linux 20.04) (after setting the necessary jpy configuration properties and calling PyLib.startPython()):
The iteration succeeds for two loops, printing Entry: __name__ -> __main__ and Entry: __doc__ -> None. At the start of the third iteration it crashes with a segmentation fault. The culprit appears to be builtins.call("next", it) in the iterator returned by PyDictWrapper.EntrySet.iterator(). This calls through to PyObject.call(). The control flow continues into PyLib_CallAndReturnObject in org_jpy_PyLib.c, and eventually to this line:
This bug manifested itself as a failure of the unit test
PyObjectTest.testDictCopy()
. It can also be triggered by the following minimal snippet (Python 3.8, 64-bit Ubuntu Linux 20.04) (after setting the necessary jpy configuration properties and callingPyLib.startPython()
):The iteration succeeds for two loops, printing
Entry: __name__ -> __main__
andEntry: __doc__ -> None
. At the start of the third iteration it crashes with a segmentation fault. The culprit appears to bebuiltins.call("next", it)
in the iterator returned byPyDictWrapper.EntrySet.iterator()
. This calls through toPyObject.call()
. The control flow continues intoPyLib_CallAndReturnObject
inorg_jpy_PyLib.c
, and eventually to this line:It is this call to PyObject_CallObject in Python's C API which directly triggers the segmentation fault.
The text was updated successfully, but these errors were encountered: