diff options
| author | 2023-05-01 16:33:22 -0400 | |
|---|---|---|
| committer | 2023-05-01 16:35:43 -0400 | |
| commit | 9fc3d279aee8175e0875f0cbe13d7cdfe92bbfa3 (patch) | |
| tree | 4bc0e9d9f0a013930c0725154bff4fb89d7c902b /libs/androidfw/StringPool.cpp | |
| parent | 269e417a53621c0457d01c58015878d9853ce946 (diff) | |
Have GrContext hold a strong ref to VulkanManager
VulkanManager is already ref counted and can be reused
across GrContext's thanks to being shared with
HardwareBitmapUploader.
So take advantage of this + the newly added skia API
for GrContext being destroyed to have GrContext hold a
strong ref to VulkanManager which in turn keeps the
VkDevice alive. If somehow we never recover from this
we'll just keep using the initial device when creating
the next Grcontext which should be fine. Memory usage
will be sub-optimal but that's better than crashing
probably.
Bug: 266626090
Test: unable to repro bug issue, so speculative fix + it didn't get
worse at least?
Change-Id: I2038dacea679c29fd098462d4cf9d298e1215fb2
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions