IssueTracker

Studio Build: 2.4 Preview 3
Version of Gradle Plugin: 2.3.0
Version of Gradle: 3.3
Version of Java: 8
OS: Windows 10 / OSX

Steps to Reproduce:

Create a project that uses CMake.  Set the project up to use ASAN (I did these steps):
Project -- build.gradle:
project.ext {
  useASAN = true
}

module -- build.gradle:
   buildTypes {
        debug {
            externalNativeBuild {
                cmake {
                    cppFlags.add("-DNDEBUG")
                    if(rootProject.ext.useASAN)
                        arguments "-DUSEASAN=ON"
                }
            }
        }

CMakeLists.txt:
option( USEASAN "asan" OFF )

if(USEASAN)
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fsanitize=address -fno-omit-frame-pointer")
set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS} -fsanitize=address")
endif(USEASAN)

Now run the app under ASAN following normal rules (enjoy results of ASAN helping you find your memory bug).  Now flip the flag in Project level build.gradle to turn off useASAN Boolean.  Observe that no amount of cleaning/cache clearing will give you a build that works.  Only solution I've found is to nuke .externalNativeBuild and build.