Fix memory leak in String16
Newly allocated SharedBuffer already has reference count 1, so we should not call acquire(). Bug: 141764153 Test: Run String16Test.* with ASan that was able to detect the leak without this change. Change-Id: Ib8b1b707b028386d717414d8c5ec5ea7b4b59464
Loading
Please register or sign in to comment