On Thu, Jun 28, 2018 at 3:11 AM, Andrew Morton
[off-list ref] wrote:

On Wed, 27 Jun 2018 17:59:00 -0700 Vishwath Mohan [off-list ref] wrote:

quoted

Yeah, I can confirm that it's an issue. Like Kostya mentioned, I don't have
data on-hand, but anecdotally both ASAN and KASAN have proven problematic
to enable for environments that don't tolerate the increased memory
pressure well. This includes,
(a) Low-memory form factors - Wear, TV, Things, lower-tier phones like Go
(c) Connected components like Pixel's visual core
<https://www.blog.google/products/pixel/pixel-visual-core-image-processing-and-machine-learning-pixel-2/>


These are both places I'd love to have a low(er) memory footprint option at
my disposal.

Thanks.

It really is important that such information be captured in the
changelogs.  In as much detail as can be mustered.

I'll add it to the changelog in v5. Thanks!