# Nemo.exe crashes after a few time steps when using AGRIF

**URL:** <https://nemo-ocean.discourse.group/t/nemo-exe-crashes-after-a-few-time-steps-when-using-agrif/469>\
**Category:** v4.2.x\
**Tags:** AGRIF\
**Created:** [31 March 2023 13:26 UTC](https://nemo-ocean.discourse.group/t/nemo-exe-crashes-after-a-few-time-steps-when-using-agrif/469 "2023-03-31T13:26:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ngrivault](https://avatars.discourse-cdn.com/v4/letter/n/df705f/32.png) [@ngrivault](https://nemo-ocean.discourse.group/u/ngrivault)\
**Post date:** [31 March 2023 13:26 UTC](https://nemo-ocean.discourse.group/t/nemo-exe-crashes-after-a-few-time-steps-when-using-agrif/469/1 "2023-03-31T13:26:16Z")

</div>

Hello everyone,

I’m setting up a 1 to 5 AGRIF nest into our NORDIC configuration with NEMO 4.2 and I’m facing a nemo.exe crash issue. The configuration consists on our NORDIC regional configuration and a nest in the Baltic inflow region.  
Initially everything was working fine for about 130 ts. Now it’s crashing after 3 (not sure what changes I made to change that). The only information I have is a unspecific libc crash:

```auto
./nemo.exe[0x44fae9]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2afb93aeb555]

```

I was able to figure out that the crash happens in the routine “Agrif\_Sponge\_tra” called in stpmlf.F90. I don’t really get any other information in the outputs.

Changing the time step didn’t change anything. Changing slightly the AGRIF child config did not change anything either. I’m up-to-date with the main development branch.

I really don’t get what can happen, and I’m exhausting my “where to look” ideas.

Thanks for your help.

---

<div class="post-metadata">

**Author:** ![jchanut](https://yyz2.discourse-cdn.com/free1/user_avatar/nemo-ocean.discourse.group/jchanut/32/9_2.png) [@jchanut](https://nemo-ocean.discourse.group/u/jchanut)\
**Post date:** [5 April 2023 13:47 UTC](https://nemo-ocean.discourse.group/t/nemo-exe-crashes-after-a-few-time-steps-when-using-agrif/469/2 "2023-04-05T13:47:09Z")

</div>

> [@ngrivault](#):
>
> I’m up-to-date with the main development branch.

Do you mean, up-to-date with the 4.2 branch or the “main” branch ?

---

<div class="post-metadata">

**Author:** ![ngrivault](https://avatars.discourse-cdn.com/v4/letter/n/df705f/32.png) [@ngrivault](https://nemo-ocean.discourse.group/u/ngrivault)\
**Post date:** [5 April 2023 14:05 UTC](https://nemo-ocean.discourse.group/t/nemo-exe-crashes-after-a-few-time-steps-when-using-agrif/469/3 "2023-04-05T14:05:47Z")

</div>

I’m up-to-date with the main branch.

---

<div class="post-metadata">

**Author:** ![jchanut](https://yyz2.discourse-cdn.com/free1/user_avatar/nemo-ocean.discourse.group/jchanut/32/9_2.png) [@jchanut](https://nemo-ocean.discourse.group/u/jchanut)\
**Post date:** [5 April 2023 15:30 UTC](https://nemo-ocean.discourse.group/t/nemo-exe-crashes-after-a-few-time-steps-when-using-agrif/469/4 "2023-04-05T15:30:59Z")

</div>

Well, the main branch has been moving a lot these past months. I would suggest you rather use the 4.2.1 branch and let me know (try to compile with debug options too).

---

<div class="post-metadata">

**Author:** ![ngrivault](https://avatars.discourse-cdn.com/v4/letter/n/df705f/32.png) [@ngrivault](https://nemo-ocean.discourse.group/u/ngrivault)\
**Post date:** [6 April 2023 12:01 UTC](https://nemo-ocean.discourse.group/t/nemo-exe-crashes-after-a-few-time-steps-when-using-agrif/469/5 "2023-04-06T12:01:36Z")

</div>

Same problem with branch\_4.2. It’s already compiled with -g -traceback, but I get nothing more specific than the libc error.