Did it start after an llvm update? Kitkat is pretty old and we don't test it upstream.
I don't see anything in the logs other than the fact that devices do not boot after asan_device_setup.

asan_device_setup that we use is a year old. This might be a problem. We should use the one from the toolchain.

I'll try this locally with LLVM ToT.

Tried locally with ToT chromium checkout on a freshly flashed hammerhead/KTU84P. Everything works perfectly.

Perhaps a device issue.

Oh wait, this is a ToT LLVM bot.

Labs: can you check if there's anything wrong with the devices connected to build3-b1?

Let me take another look. It could be an asan problem after all.

Reproduced. Seems to be caused by http://llvm.org/viewvc/llvm-project?rev=317943&view=rev

Can we revert? We're trying to do a clang roll and this now sounds like a blocker.

There are several changes on top that one.
I'll try to disable the new feature with a flag.

Fixed in http://llvm.org/viewvc/llvm-project?view=revision&revision=318369

And the first build that includes my change is stuck in the compilation step for 9 hours:
https://build.chromium.org/p/chromium.clang/builders/ToTAndroidASan/builds/201

I'm pretty sure it is unrelated.

Yes, it seems builds on that machine are always very slow. It seems to be a 4-core 16 GB machine which isn't so great when it can't use goma..