Segmentation fault on jl.seval("using ...")

**Affects:** JuliaCall

**Describe the bug**
In the package [pdaqp](https://github.com/darnstrom/pdaqp) I am using juliacall to wrap the Julia package [ParametricDAQP.jl](https://github.com/darnstrom/ParametricDAQP.jl)
I have not observed this myself, but we have had some problems with segmentation faults on `ubuntu-latest` runners when `pdaqp` is used in [cvxpygen](https://github.com/cvxgrp/cvxpygen), and now other users have also started observing this.

**Your system**
Since I am not able to reproduce the segmentation fault on my own system, an example of when the problem arises is given in [this issue](https://github.com/cvxgrp/cvxpygen/issues/88). Where some system information and a trace is given.

**Additional context**
Is there some best practices here that I can use to avoid segmentation faults. I have based a lot of the wrapper on how [PySR](https://github.com/MilesCranmer/PySR) uses juliacall, so maybe @MilesCranmer have some insight?
Here is the section of pdaqp where juliacall is setup:
https://github.com/darnstrom/pdaqp/blob/bf511826beae525b794537dd7b413d6005e7a9ad/src/pdaqp/pdaqp.py#L1C1-L16C34
The segmentation fault seems to happen on line 15: jl.seval("using ParametricDAQP")

Start with the pdaqp setup in src/pdaqp/pdaqp.py, especially the jl.seval("using ParametricDAQP") call on line 15, then review the system information and trace in cvxpygen issue 88. Compare the reported ubuntu-latest conditions and Julia/PythonCall usage; done means identifying a reproducible cause or documenting actionable guidance to avoid the segmentation fault.

Written by the indexing model from the issue text.