https://build.chromium.org/p/chromium.fyi/builders/CrWinAsan%20tester/builds/943/steps/sbox_integration_tests/logs/AddressSanitizerTests.TestAddressSanitizer

AddressSanitizerTests.TestAddressSanitizer (run #1):
[ RUN      ] AddressSanitizerTests.TestAddressSanitizer
..\..\sandbox\win\srcddress_sanitizer_test.cc(96): error: Value of: strstr(data.c_str(), strrchr(__FILE__, '\'))
  Actual: false
Expected: true
The stack trace doesn't have a correct filename:
=================================================================
==4936==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x04a01c18 at pc 0x00f411bd bp 0xdeadbeef sp 0x0032fb90
WRITE of size 4 at 0x04a01c18 thread T0
    #3 0x158026b in __scrt_common_main_seh f:\ddctools\crtcstartup\src\startup\exe_common.inl:264
    #4 0x75f33379 in BaseThreadInitThunk+0x11 (C:\Windows\syswow64\kernel32.dll+0x13379)
    #5 0x77d39881 in RtlInitializeExceptionChain+0x62 (C:\Windows\SysWOW64
tdll.dll+0x39881)
    #6 0x77d39854 in RtlInitializeExceptionChain+0x35 (C:\Windows\SysWOW64
tdll.dll+0x39854)

0x04a01c18 is located 0 bytes to the right of 168-byte region [0x04a01b70,0x04a01c18)
allocated by thread T0 here:
    #0 0x1569be8 in malloc c:uild\slave\crwinasanuild\src	hird_party\llvm\projects\compiler-rt\libsansan_malloc_win.cc:63
    #1 0x157fdc6 in operator new f:\ddctools\crtcstartup\src\heap
ew_scalar.cpp:19
    #5 0x158026b in __scrt_common_main_seh f:\ddctools\crtcstartup\src\startup\exe_common.inl:264
    #6 0x75f33379 in BaseThreadInitThunk+0x11 (C:\Windows\syswow64\kernel32.dll+0x13379)
    #7 0x77d39881 in RtlInitializeExceptionChain+0x62 (C:\Windows\SysWOW64
tdll.dll+0x39881)
    #8 0x77d39854 in RtlInitializeExceptionChain+0x35 (C:\Windows\SysWOW64
tdll.dll+0x39854)



Possibly triggered by https://chromium.googlesource.com/chromium/src/+/f9b843b964801440b50e74b072c70e7ecb0f1921%5E%21/#F5 somehow, but it's also the first test run on the bot in 11 days.