SurfaceClass: Add validity checks for D3D surface before operations - #64
Merged
Conversation
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
1 participant
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.
Fixes CLIENT-EW. The issue was that: Direct3D surface creation failure propagates a null pointer, causing an access violation when
SurfaceClass::Lockattempts dereference.Is_Valid()method toSurfaceClassto check the underlying D3D surface.Get_Description,Lock,Unlock,Clear,Copy,CreateCopy,CopyRect,CopyCol,FindBB,Is_Transparent_Column,Get_Pixel,DrawPixel,DrawHLine,Is_Monochrome, andHue_Shift.Render2DSentenceto ensure the surface is valid after creation and before locking, handling potential failures gracefully.This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 1899838
Not quite right? Click here to continue debugging with Seer.