commit 4981b193dea6d31249f9dfe64239ab9b07017cf1
author Kostya Kortchinsky <kostyak@google.com> Mon Sep 28 17:21:00 2020 -0700
committer Copybara-Service <copybara-worker@google.com> Tue Sep 29 14:07:37 2020 -0700
tree 52d8c58fadb2b411112a2c7c971846bc5b09d7e5
parent a2d92a39072bf0ca5181d8f1908f4a9695216be4

[scudo][standalone] Fix Primary's ReleaseToOS test

Said test was flaking on Fuchsia for non-obvious reasons, and only
for ASan variants (the release was returning 0).

It turned out that the templating was off, `true` being promoted to
a `s32` and used as the minimum interval argument. This meant that in
some circumstances, the normal release would occur, and the forced
release would have nothing to release, hence the 0 byte released.

The symbols are giving it away (note the 1):
```
scudo::SizeClassAllocator64<scudo::FixedSizeClassMap<scudo::DefaultSizeClassConfig>,24ul,1,2147483647,false>::releaseToOS(void)
```

This also probably means that there was no MTE version of that test!

Differential Revision: https://reviews.llvm.org/D88457

GitOrigin-RevId: e456df77c2a5a2bf905f6848a09faf69b49c5752