Fix: deallocate in metapackage_t destroy() - #1192
Merged
perazz merged 1 commit intoOct 11, 2025
Merged
Conversation
perazz
approved these changes
Oct 11, 2025
perazz
left a comment
perazz
left a comment
Member
There was a problem hiding this comment.
Great catch, thank you @SamueleGiuli.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a runtime error caused by attempting to allocate an already allocated variable in the
init_minpacksubroutine.The root cause was that the
destroy(this)subroutine of in fpm_meta_base.f90 did not deallocate thedependencyallocatable array that was previously allocated in the subroutineinit_stdlib, which led to a double-allocation error when callingallocate(this%dependency(1))insideinit_minpack.