Segmentation fault when calling `quit()` on a job event listener about pythonmonkey HOT 6 CLOSED

stack looks like

Thread 1 "python" received signal SIGSEGV, Segmentation fault.
0x00007ffff768597e in FuncType::getPyObject (cx=0x55555561b3f0, fval=...)
at /home/philippe/Sources/PythonMonkey/src/FuncType.cc:19
19 proxy->jsFunc->set(&fval.toObject());
(gdb) bt
#0 0x00007ffff768597e in FuncType::getPyObject (cx=0x55555561b3f0, fval=...)
at /home/philippe/Sources/PythonMonkey/src/FuncType.cc:19
#1 0x00007ffff76c605e in pyTypeFactory (cx=0x55555561b3f0, rval=...)
at /home/philippe/Sources/PythonMonkey/src/pyTypeFactory.cc:108
#2 0x00007ffff76b8ef4 in enqueueWithDelay (cx=0x55555561b3f0, argc=4, vp=0x7fffffffb998)
at /home/philippe/Sources/PythonMonkey/src/internalBinding/timers.cc:34
#3 0x000026506dd3de1b in ?? ()
#4 0x00001327f7a5d780 in ?? ()
#5 0x00007fffffffb970 in ?? ()
#6 0x0000000000000000 in ?? ()

from pythonmonkey.

@wiwichips
This is due to quit not being async, (all other functions in the example are async) and is thus not supported without an async wrapper such as

async def async_quit():
quit()

my_j.on('accepted', lambda: async_quit())

from pythonmonkey.

Even if its unsupported, it should result in an exception, not a segmentation fault

from pythonmonkey.

also works fine if not using lambda:
def non_async_quit():
quit()

my_j.on('accepted', non_async_quit())

from pythonmonkey.

just made an incorrect pr closes comment

from pythonmonkey.

note same result if call exit or sys.exit

from pythonmonkey.