Fix memory leak in CreateTexture and bump version to 1.2.0 #72
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 addresses a memory leak issue where
UPackageobjects were not properly cleaned up if the texture generation process was cancelled or failed (specifically during package creation).Key changes:
UPackage*withTStrongObjectPtr<UPackage>to better manage the object lifecycle.RF_StandaloneandRF_MarkAsRootSetflags and callMarkAsGarbage()if the operation is cancelled before the package is marked dirty (saved).ShouldCancel()checks to occur immediately afterEnterProgressFrame()to catch cancellation events as early as possible.Note on Error Handling: The existing logic for texture processing errors (e.g., unsupported format) intentionally continues execution to produce a result (even if partial/black), preserving the user's workflow. Therefore, explicit package destruction is not applied in those loops to maintain existing behavior.
PR created automatically by Jules for task 1289736565483385526 started by @EmbarrassingMoment