Hi @baubin
It is hard to say without a test that can be run and fails, your initial test should work stand-alone.
What it seems is that something is using multi-threading, either in pytest or in your code and in that case you need to attach each thread to the jvm with the jvm.attachCurrentThread(). See Python wrapper and orekit.initVM()
What is a known bug is the combination of pycharm’s debug feature that asynchronously gets values of object, that is often crashing orekit, we have not been able to track down the source of this. This can be mitigated by setting the Pycharm loading to on-demand.
@nattip hard to say but seems like your stack is overflown. Try to increase the JVM max stack memory allocation, the vmargs can be set through the .initVM(vmargs=str ) where str is jvm start parameters. I think the stack is -XmxZZ for stack but please goolge. Likely something isn’t right if you run out of stack.