Skip to content

CodeQL Potential use after free fix#1024

Open
NullVerdict wants to merge 4 commits intoTheAssemblyArmada:vanillafrom
NullVerdict:vanilla
Open

CodeQL Potential use after free fix#1024
NullVerdict wants to merge 4 commits intoTheAssemblyArmada:vanillafrom
NullVerdict:vanilla

Conversation

@NullVerdict
Copy link

CodeQL detected errors like Potential use after free. I recommend integrating CodeQL into your development process to detect and fix many more such vulnerabilities.

NullVerdict and others added 3 commits November 5, 2024 21:38
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Fix code scanning alert no. 96: Potential use after free
@giulianobelinassi
Copy link
Collaborator

Have you tested this with address sanitizer or valgrind to check if this doesn´t introduce any memory leaks?

Copy link
Contributor

@OmniBlade OmniBlade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks legit, only reason it doesn't blow up is because these objects are allocated off the games heap classes so the memory is still actually allocated to the game.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants