-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WRFDA PLUS V4.6.0 fails with intel llvm compilers. #2048
Comments
I'd caution to label this as a "memory leak" as that has technical implications of the underlying root cause. It is a memory usage issue with large files when compiling with the new oneAPI compilers, however. Consider compiling with a very limited number of threads (some files require upwards of 25GB individually) until a future fix is implemented. |
I will change the title of the issue to reflect that. |
I have tried with 4 threads and it still faults the machine. Should I attempt with 1 or 2 threads to help you with this issue @islas ? |
Definitely try just one thread. It will be much slower but it should compile at the very least. |
Tried one thread and it worked, opened 4 posts on the wrf forum about this and my tests. I'll leave it to you to let me know if you need me to do more testing or create pull requests. Here are the links: https://forum.mmm.ucar.edu/threads/wrf-chem-w-kpp-wrf-chemda-v4-6-0-intel-llvm-compilers.17266/ https://forum.mmm.ucar.edu/threads/wrf-arw-v4-6-0-intel-llvm-compilers.17265/ https://forum.mmm.ucar.edu/threads/wrf-4dvar-v4-6-0-intel-llvm-compilers.17264/ https://forum.mmm.ucar.edu/threads/wrf-plus-4dvar-v4-6-0-intel-llvm-compilers.17263/ |
Closing issue and opening again with new information |
@islas @mgduda
Describe the bug
During the installation of WRFPLUS v4.6.0 a massive memory usage occurs that happens only with the intel llvm compilers and not with GNU.
I have attached relevant log files.
configure.log
configure.wrf.txt
wrfplus1.compile.log
To Reproduce
Expected behavior
No Memory leak
Screenshots
The text was updated successfully, but these errors were encountered: