Add (slightly hacky) clearing of init contents after capture

* This eliminates most of the leaking on capture - other than this it's
  mostly the leaking serialisation which isn't a huge deal (this could
  be ~900MB-1GB a capture.
This commit is contained in:
baldurk
2016-02-07 18:43:54 +01:00
parent ff26fabc7f
commit 04a2e2ad2a
4 changed files with 30 additions and 13 deletions
-1
View File
@@ -31,7 +31,6 @@ On capture:
* Memory maps are not intercepted, so any modifications are saved by reading back from the mapped pointer, even if it is uncached/write combined.
* Image contents are saved out by copying aliasing their backing memory to a buffer, so will not be GPU-portable.
* Captures will not be GPU-portable where memory indices etc change.
* Memory leaks each time a new capture is created.
* Unsupported or untested features:
* Subpasses
* Nested command buffer execution