-
Notifications
You must be signed in to change notification settings - Fork 714
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
only memory leak related #2139
base: develop
Are you sure you want to change the base?
only memory leak related #2139
Conversation
The regression test results:
|
1 similar comment
The regression test results:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks safe for release branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be committed before PR #2137 if we want to separate the changes, but it is also contained in that PR.
…ofile after RETURN logic
TYPE: bug fix
KEYWORDS: Memory Leaks
SOURCE: Charlie Li - Software developer from lakes environmental Canada
DESCRIPTION OF CHANGES:
Problem:
Memory leaks are detected in wrf_timeseries.F and start_em.F when use PGI option:
-g -O0 -traceback -Mchkptr -Mbounds -Ktrap=fp -Msave -tp=px
It will failed for: "0: ALLOCATE: array already allocated"
Solution:
Calls to deallocate the array dz8w is added, and move the return statement before array allocation.
LIST OF MODIFIED FILES:
M share/wrf_timeseries.F
M dyn_em/start_em.F
TESTS CONDUCTED:
The Jenkins tests are all passing.
RELEASE NOTE: This PR fixed a memory leak related to arrays being allocated without being deallocated in start_em and time series calculation subroutine.