Exception caught when I called SharedInterpreter.close() function with a High-frequency calling.

nomiuo commented 1 year ago

Describe the bug I had an object pool in a python module which was imported into the SharedInterpreter. I don't know if this caused this exception.

When I created a SharedInterpreter, did sth and close it in one thread with a High-frequency calling, an execption was caught and raised.

Maybe the pyobject was changed in pool and the closing operation was done at the same time?

The number of PyObjects was getting bigger quickly.

After a while, my jvm crashed...

Expected behavior How to fix it?

Environment (please complete the following information):

OS Platform, Distribution, and Version: Ubuntu 22.04
Python Distribution and Version: CPython 3.9.13
Java Distribution and Version: openjdk version "1.8.0_362"
Jep Version: 4.1.1
Python packages used (e.g. numpy, pandas, tensorflow): rpyc

ndjensen commented 1 year ago

Why did you close the ticket? Are you synchronizing externally? We should be able to fix the ConcurrentModificationException. I'm not sure how much that relates to the crash, but it looks like MemoryManager isn't thread safe.

nomiuo commented 1 year ago

Sorry. I forgot to close the object, so the jvm crashed...

ninia / jep

Exception caught when I called SharedInterpreter.close() function with a High-frequency calling. #460