This error didn’t really block my build, and since Android Studio trims down long outputs I never fully realised how many exceptions I was actually getting.
But then I found some log files whose size was ~1GB and even ~5GB!įailed to execute .btree.FreeListBlockStore$FreeListBlock.alloc(FreeListBlockStore.java:222) Most of the log files in these folder are 1-2 MB or less. Now this folder contains hundreds of log files for daemons spawned by different versions of gradle gradle/daemon/ folder’s size was ~ 15GB. gradle folder and try to find out where all the storage is going. It was around 1.5GB, nothing suprising here. The first thought was to check downloaded library caches in caches/modules-2/files-2.1. gradle folder and found it’s size to be 28GB. I remained skeptical since then where is disk memory going, since I could not find anything suspicious in Storage Manager.Īt this point I already know my usual culprits - docker images, emulator images, Android sdk platform sources but I had already optimised these few days ago so these definitely didn’t cause any problem. To get things working fast, I removed all local docker images and caches to reclaim around 10GB of memory enough to get my work going. Now I’ve had problems with my storage of my MacBook in past too but the situation never became this dire. I had suddenly run out of all my disk memory. I checked Storage Manager and it showed me 16MB of free space left. > java.io.IOException: No space left on device A failure occurred while executing .tasks.PackageAndroidArtifact$IncrementalSplitterRunnable
0 kommentar(er)
