Received from Omarjan Obulkasim (Sun Yat-sen University):
I am currently working on coupling the Simstrat model with a regional climate model. During this process, I observed a potential memory leak issue within Simstrat. Specifically, the model defines numerous allocatable variables, but it appears that many of these are not explicitly deallocated. As a result, when Simstrat is embedded within a larger modeling framework such as a regional climate model, this can lead to significant memory issues over time.
While modern compilers may automatically reclaim some of the memory, relying solely on this behavior can cause problems in long-term coupled simulations. In my case, it has led to memory leaks that affect the stability and performance of the entire coupled system.
I would like to report this issue to you. Explicitly deallocating memory where appropriate would likely resolve the problem and improve Simstrat's robustness in coupled applications.
Received from Omarjan Obulkasim (Sun Yat-sen University):
I am currently working on coupling the Simstrat model with a regional climate model. During this process, I observed a potential memory leak issue within Simstrat. Specifically, the model defines numerous allocatable variables, but it appears that many of these are not explicitly deallocated. As a result, when Simstrat is embedded within a larger modeling framework such as a regional climate model, this can lead to significant memory issues over time.
While modern compilers may automatically reclaim some of the memory, relying solely on this behavior can cause problems in long-term coupled simulations. In my case, it has led to memory leaks that affect the stability and performance of the entire coupled system.
I would like to report this issue to you. Explicitly deallocating memory where appropriate would likely resolve the problem and improve Simstrat's robustness in coupled applications.