Sudden segmentation violation error in CalculiX

Hi all,

I have an issue with my FSI simulations using OpenFOAM and CalculiX where the simulation runs for a while but suddenly terminates in CalculiX with the following error

Adapter writing coupling data…
Writing DISPLACEMENTDELTAS coupling data with ID ‘2’.
Adapter calling advance()…
—[precice] e[0m relative convergence measure: relative two-norm diff of data “DisplacementDelta” = 2.18e-06, limit = 1.00e-03, normalization = 1.90e-03, conv = true
—[precice] e[0m relative convergence measure: relative two-norm diff of data “Force” = 4.45e-05, limit = 1.00e-03, normalization = 2.63e+04, conv = true
—[precice] e[0m All converged
[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see https://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run
[0]PETSC ERROR: to get more information on the crash.
[0]PETSC ERROR: User provided function() at unknown file:0
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 59.

I am running OpenFOAM in parallel but not CalculiX. I don’t have any convergence issues prior to the error, and there appears to be nothing wrong in OpenFOAM, so I can’t work out what is causing the error.

Any help or advice would be greatly appreciated.

Many thanks,
Rachael

As me and @rachaelesmith have already discussed, we suspect that this is yet another instance of Check for memory leaks · Issue #10 · precice/calculix-adapter · GitHub.

See also CalculiX adapter memory just keeps growing and Large memory usage while running.