GitLab

For vulkan 1.1.0, VmaAllocator will use dedicated memory
allocation for some big vulkan memory request, and free
it when the allocation is released. Without this change,
the VmaAllocator will allocate memory from self managed
memory blocks for all vulkan memory request. And the
memory may not be released when the allocation is
released. VmaAllocator may keep the memory for later
usage. It could be the reason for the memory regression
in fuchsia.

Bug: fuchsia:52463
Change-Id: I7b905435d31b927b2344724f8a2e1738e0544410
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215414
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Auto-Submit: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#771927}