With this update, the IDE now check the directories that could be impacted by this and recommends how to fix this issue. Scanning those takes up a lot of I/O and CPU bandwidth. The reason for this, it turned out, was that many anti-virus programs would scan Android Studio’s build targets - and these have a lot of small files. Developers on Microsoft’s platform often complained about how their build times were getting slower. One interesting update will bring a welcome change to Android Studio users on Windows. The Android Emulator now also uses fewer CPU resources, often by up to 3x.

The team also addressed user interface freezes and improved both build and overall IDE speed.

It’s now also easier for developers to share their memory problems with Google. Over the last year, the team fixed 33 major memory leaks and a new feature allows the IDE to collect more information about how it uses memory and suggest memory settings for you. One of the things that slowed Android Studio down were memory leaks, for example. The most important updates probably focus on speed. “We are certainly not done improving quality with Android Studio, but with the work and new infrastructure put into Project Marble we hope that you are even more productive in developing Android apps,” the company notes in today’s announcement. Android Studio 3.5, which the company is launching today, is the result of these efforts. Over time, though, as Google extended Android Studio, it started to slow down. That was in marked contrast to previous updates, where the focus was very much on adding new features. At last year’s I/O developer conference, Google announced Project Marble, an effort to bring more speed and stability to the company’s Android Studio IDE.

Android studio ide slow