Skip to content

MissileLauncherBuildingUpdate: Add safety check for destroyed objects - #66

Draft
seer-by-sentry[bot] wants to merge 1 commit into
mainfrom
seer/fix/missile-launcher-building-update-safety
Draft

MissileLauncherBuildingUpdate: Add safety check for destroyed objects#66
seer-by-sentry[bot] wants to merge 1 commit into
mainfrom
seer/fix/missile-launcher-building-update-safety

Conversation

@seer-by-sentry

Copy link
Copy Markdown

Fixes CLIENT-C5. The issue was that: Module data was set to NULL during object destruction, but concurrent special power execution attempted to dereference the cleared pointer.

  • Added safety checks to MissileLauncherBuildingUpdate::updateModelCondition, MissileLauncherBuildingUpdate::update, and MissileLauncherBuildingUpdate::getTemplate to prevent accessing module data after the object has been destroyed.
  • This prevents potential crashes or undefined behavior when the module data pointer is invalid.

This fix was generated by Seer in Sentry, triggered by x64-dev. 👁️ Run ID: 1901147

Not quite right? Click here to continue debugging with Seer.

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.

0 participants