SIGSEGV at end thrown in v1.5.2 but not in previous version

[petrushy]

Hi,

I have quite little info yet, but in the tests we have in the project orekit the new 1.5.2 is throwing a SIGSEV at the end of tests while it works with 1.5.1, 1.5.0.

It comes at the very end after tests are (successfully) concluded, so I guess it has to do with the shutdown of the JVM.

It happens when pytest itself discovers the tests, if i run them one by one it does not appear.

The MR for orekit is at https://gitlab.orekit.org/orekit/orekit_jpype/-/merge_requests/26

I can reproduce this outside the CI by running "uv run python3 -m pytest" in the test dir.

Sorry for the fragmented information but in case it gives some hints it would be good.

[Thrameos]

There was some code changed on shutdown. Perhaps it is a race condition that got introduced with the non-ansi cleanup.

If you gat get me a reduced example I can look at it.