segmentation fault (SIGSEGV) when computing neighbors

[Hrovatin]

Please make sure these conditions are met

• I have checked that this issue has not already been reported.
• I have confirmed this bug exists on the latest version of scanpy.
• (optional) I have confirmed this bug exists on the main branch of scanpy.

What happened?

Issue in computing neighbors. Likely env dependent, but given env is fresh I was hoping you may provide some guidance

Fresh env:

python==3.10
numba==0.61.0
numpy==1.26.4
scanpy==1.11.0
scipy==1.15.2
# using CONDA_SUBDIR=osx-64 for mamba env creation on M3 chip
# Other packages omitted

Try running neighbors:

sc.pp.neighbors(emb,n_pcs=30)
/Users/karinhrovatin/miniforge3/envs/protein/lib/python3.10/site-packages/threadpoolctl.py:1226: RuntimeWarning: 
Found Intel OpenMP ('libiomp') and LLVM OpenMP ('libomp') loaded at
the same time. Both libraries are known to be incompatible and this
can cause random crashes or deadlocks on Linux when loaded in the
same Python program.
Using threadpoolctl may cause crashes or deadlocks. For more
information and possible workarounds, please see
    https://github.com/joblib/threadpoolctl/blob/master/multiple_openmp.md
  warnings.warn(msg, RuntimeWarning)
OMP: Info #276: omp_set_nested routine deprecated, please use omp_set_max_active_levels instead.
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

The packages libiomp and libomp are not within conda env (at least not seen via pip freeze).
Already tried export OMP_NUM_THREADS=1 that was mentioned in another issue.

Minimal code sample

see above

Error output

Versions

See above

[ilan-gold]

But @Hrovatin what system are you on? Mac? Linux? Could you give a clean reproducer? If this is truly a dependency issue, it should be as simple as (a) install some packages and hten (b) attempt to run the code on a very small anndata (i.e., no need for data sharing)