[Mesa-users] Unexpected termination

[Warrick Ball]

Hi Debasish,

This means the operating system has decided to terminate your run, which is usually because you've run out of RAM.

You can try turning on the basic "garbage collector":

     https://docs.mesastar.org/en/release-r22.11.1/reference/star_job.html#num-steps-for-garbage-collection

which might help if the main problem is a long running job that's building up a lot of EOS tables in memory.

If you're using a virtual machine, you might need to allocate more RAM to it.

A quick search for "killed" in the mailing list archive or in the documentation turns up this same answer. e.g.

     https://lists.mesastar.org/pipermail/mesa-users/2022-July/013919.html
     https://docs.mesastar.org/en/release-r22.11.1/faq.html#why-does-mesa-fail-to-build-when-testing-the-eos-module

Cheers,
Warrick

___________

Warrick Ball
Senior Research Software Engineer
University of Birmingham
W.H.Ball at bham.ac.uk

On Sat, 21 Jan 2023, mesa-users at lists.mesastar.org wrote:

> Hi,I have been trying to evolve a 30 solar mass star till core collapse. For that I have made some changes in the 12M_pre_ms_to_core_collapse test suite. But, I could not evolve it beyond Helium burning. I am getting an termination message 
> 
> ./rn1: line 6: 32560 Killed                  ./star
> DATE: 2023-01-21
> TIME: 17:38:37
> 
> ******************************************************************
> failed to create after_core_he_burn.mod when running inlist_to_end_core_he_burn_header
> ******************************************************************
> Thanks and regards,
> Debasish
> 
> 
>