# Problem with MPI Fortran code

**URL:** <https://fortran-lang.discourse.group/t/problem-with-mpi-fortran-code/7040>\
**Category:** Help\
**Created:** [December 24, 2023, 9:49am UTC](https://fortran-lang.discourse.group/t/problem-with-mpi-fortran-code/7040 "2023-12-24T09:49:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![wyphan](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/wyphan/32/632_2.png) [@wyphan](https://fortran-lang.discourse.group/u/wyphan)\
**Post date:** [December 27, 2023, 6:14pm UTC](https://fortran-lang.discourse.group/t/problem-with-mpi-fortran-code/7040/4 "2023-12-27T18:14:12Z")

</div>

@aerosayan There are certain edge cases tho, like with module variables and when using `SAVE`. In-depth discussion here:

> [@Best practice: Deallocating allocatable arrays explicitly vs implicitly](https://fortran-lang.discourse.group/t/best-practice-deallocating-allocatable-arrays-explicitly-vs-implicitly/3071):
>
> Allocatable errorsarrays are deallocated automatically once they are out of scope, i.e. at the end of the procedure they are declared. Should one still use explicit deallocation? (If you want to deallocate early then you have to do it explicitly of course.)

---

_[View the full topic](https://fortran-lang.discourse.group/t/problem-with-mpi-fortran-code/7040)._