commit 244ebf7d5e86f4800606198ae4dc8f3a028aece5
author John Stiles <johnstiles@google.com> Wed Oct 28 11:08:06 2020 -0400
committer Skia Commit-Bot <skia-commit-bot@chromium.org> Wed Oct 28 15:59:51 2020 +0000
tree 7c7825a3c6c97f2931397369372fa16de75ca80b
parent 4ce77863d5838cc16760f9b0a71020854b718d32

Add `reportLeaks` method to GrMemoryPool.

This doesn't change any behavior; it just exposes existing code that
previously could only run at ~GrMemoryPool time. Now you can report
leaks on a memory pool without actually destroying it.

Change-Id: I35bf6c7d886827031cce0e2b045775207062c121
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/330217
Commit-Queue: John Stiles <johnstiles@google.com>
Commit-Queue: Brian Osman <brianosman@google.com>
Auto-Submit: John Stiles <johnstiles@google.com>
Reviewed-by: Brian Osman <brianosman@google.com>

src/gpu/GrMemoryPool.cpp

diff --git a/src/gpu/GrMemoryPool.cpp b/src/gpu/GrMemoryPool.cpp
index b580531..2686cbf 100644
--- a/src/gpu/GrMemoryPool.cpp
+++ b/src/gpu/GrMemoryPool.cpp
@@ -34,6 +34,12 @@
 }
 
 GrMemoryPool::~GrMemoryPool() {
+    this->reportLeaks();
+    SkASSERT(0 == fAllocationCount);
+    SkASSERT(this->isEmpty());
+}
+
+void GrMemoryPool::reportLeaks() const {
 #ifdef SK_DEBUG
     int i = 0;
     int n = fAllocatedIDs.count();
@@ -47,8 +53,6 @@
         }
     });
 #endif
-    SkASSERT(0 == fAllocationCount);
-    SkASSERT(this->isEmpty());
 }
 
 void* GrMemoryPool::allocate(size_t size) {