IssueTracker

Indexing also runs indefinitely here with Android studio 3.3 and a project that contains a NDK library (native engine + game). Previous versions, for instance 3.2.1, worked fine. Still occurs after clearing the caches and deleting the .idea folder. On a desktop with 32 GB of RAM it's not running out of memory but it indexes forever, pegging an entire CPU and disk access to 100%, and it never stops. The same thing occurs with gradle 4.6 or 4.10. If I enable the experimental scan active configuration only setting, everything is basically broken - no syntax highlighting, cpp files don't show. Waiting to see if there's a workaround before reverting to 3.2.1 and being much more cautious about updating in the future ..

When I let it run for hours, the scanning eventually did complete, then the indexing took more hours, I let it run as well, and eventually it switched to 'building symbols' which also started taking a long time without progress, but that, eventually, crashed Android Studio with an out of memory error, telling me to increase the heap size. I did, and upon restarting Android Studio, it started over at scanning .. so I gave up for now. This is with a mid-size NDK project.

Even after a dirty downgrade to AS 3.2 from 3.3 my project was stuck on scanning files to index and building symbols. I ended up having to fully remove all Android Studio files/folders. After relaunching AS 3.2 and setting heap size to 8GB the scanning, indexing and building symbols took just a couple minutes.

These were the folders I deleted:
rm -rfv ~/Library/Application\ Support/AndroidStudio*
rm -rfv ~/Library/Preferences/AndroidStudio*
rm -rfv ~/Library/Caches/AndroidStudio*
rm -rfv ~/Library/Logs/AndroidStudio*
rm -rfv ~/.AndroidStudio*

Any chance someone has a repro project they can share?
@brigham, are you saying deleting those folders help with your issue?

@tianyu, just a heads up, this may be related to the configuration cache issue you've been looking at.

I am facing the exact same issues here. I have two projects where I build native code outside of Android Studio (Cygwin shell + ndk-build.cmd) and that goes fine in AS 3.3. But one project where I use externalNativeBuild in the gradle file has the same issues as described here. The native library part is not that big (couple of .cpp and ..h files). It is like it is scanning the entire NDK. Switching back to AS 3.2 solves it.

Update: if I use Process Monitor I can see it scan my entire disk: studio64.exe accesses even my Pictures folder!

Thanks Jomo and everyone. We recently identified a bug that could be related to this.

Hi Davy, can you share the directory structure of your project. Where is the NDK located with respect to the project? Also where are your cpp files with respect to the rest of the project files?