Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory not properly released. #3

Open
mld2443 opened this issue Oct 25, 2018 · 2 comments
Open

Memory not properly released. #3

mld2443 opened this issue Oct 25, 2018 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@mld2443
Copy link
Owner

mld2443 commented Oct 25, 2018

D3D12 Device resources still remain allocated at program termination.

Need to switch to using comPtrs or std::unique_ptrs for memory management, because this can start getting ugly.

@mld2443 mld2443 added the bug Something isn't working label Oct 25, 2018
@mld2443 mld2443 added this to the First Working Tutorial milestone Oct 25, 2018
@mld2443 mld2443 self-assigned this Oct 25, 2018
@mld2443
Copy link
Owner Author

mld2443 commented Nov 2, 2018

I now utilize ComPtrs and the memory model is clean as a whistle.

@mld2443 mld2443 closed this as completed Nov 2, 2018
@mld2443 mld2443 reopened this Aug 14, 2020
@mld2443
Copy link
Owner Author

mld2443 commented Aug 14, 2020

Now that I have enabled debug information for DXGI (in addition to D3D12), it has revealed that pretty much all D3D12 and DXGI objects are being kept alive somehow. This is a problem as I intended for this program to be something of a role model, even if no one else ever uses it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant