Intermittent 'AddressSanitizer CHECK failed' error

[isar...@google.com]

We run ASAN on AARCH64 platoform (Brillo codebase) and intermittently run into the following error.  Any idea why and how to avoid this?

=8465==AddressSanitizer CHECK failed: external/compiler-rt/lib/sanitizer_common/sanitizer_allocator.h:1057 "((IsAligned(map_beg, page_size_))) != (0)" (0x0, 0x0)
    #0 0x7fa691e9ab  (/system/lib64/libclang_rt.asan-aarch64-android.so+0x6f9ab)
    #1 0x7fa692a5cb in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/system/lib64/libclang_rt.asan-aarch64-android.so+0x7b5cb)
    #2 0x7fa68cdf53  (/system/lib64/libclang_rt.asan-aarch64-android.so+0x1ef53)
    #3 0x7fa68cdafb  (/system/lib64/libclang_rt.asan-aarch64-android.so+0x1eafb)
    #4 0x7fa68cad73 in __cxa_finalize (/system/lib64/libclang_rt.asan-aarch64-android.so+0x1bd73)
    #5 0x7fa6920a23 in operator new(unsigned long) (/system/lib64/libclang_rt.asan-aarch64-android.so+0x71a23)
    #6 0x5555b04dd3 in std::__1::__allocate(unsigned long) external/libcxx/include/new:168:10
    #7 0x5555b04dd3 in std::__1::allocator<unsigned char>::allocate(unsigned long, void const*) external/libcxx/include/memory:1720
    #8 0x5555b04dd3 in std::__1::allocator_traits<std::__1::allocator<unsigned char> >::allocate(std::__1::allocator<unsigned char>&, unsigned long) external/libcxx/include/memory:1479
    #9 0x5555b04dd3 in std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >::allocate(unsigned long) external/libcxx/include/vector:928 

#10 0x5555b04dd3 in std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >::vector(unsigned long, unsigned char const&) external/libcxx/include/vector:1099 

[Konstantin Serebryany]

+alekseys, who has been touching this code recently. 

--
You received this message because you are subscribed to the Google Groups "address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to address-sanitizer+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aleksey Shlyapnikov]

This is indeed unexpected, since this check verifies that memory returned by mmap() call is page size aligned. If you can trace mmap calls to see what was actually returned or add a debug print and rebuild ASan library, that might help to shed some light on what triggers this assert.

On Mon, Mar 26, 2018 at 4:58 PM, Konstantin Serebryany <konstantin....@gmail.com> wrote:

+alekseys, who has been touching this code recently. 

[isar...@google.com]

alekseys and I have been working on this offline, will update as soon as we figure this out. Thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to address-saniti...@googlegroups.com.