The IDE Can't handle decoupled projects

[Rafael2616]

Hi dev, I'm super excited with your work on the IDE, so I can tell you that very large or even minium multimodule projects are impossible to run, i think this was start to happen with new tooling API implementation or indexing API much time ago by the old Android IDE developer. So the point is that the big project consume excessive RAM, my device has 12 Gb RAM+ 4 Ram boost + powerful CPU and even the application crashes with Out of Memory. I would be very happy if this problem could be identified and fixed. My project has about 16 modules and it is Kotlin multiplataform

Here is the stack:

AndroidIDE Crash Report
Version : v1.0.0+gh.r01 (1000)
Variant : arm64-v8a (release)
Build type : UNOFFICIAL
SDK Version : 35
Supported ABIs : [arm64-v8a]
Manufacturer : motorola
Device : motorolaedge60pro

Stacktrace:
java.lang.OutOfMemoryError: Failed to allocate a 224 byte allocation with 558512 free bytes and 545KB until OOM, target footprint 536870912, growth limit 536870912; giving up on allocation because <1% of heap free after GC.
at android.view.DisplayInfo$1.createFromParcel(DisplayInfo.java:395)
at android.view.DisplayInfo$1.createFromParcel(DisplayInfo.java:392)
at android.os.Parcel.readTypedObject(Parcel.java:4218)
at android.hardware.display.IDisplayManager$Stub$Proxy.getDisplayInfo(IDisplayManager.java:1399)
at android.hardware.display.DisplayManagerGlobal$1.recompute(DisplayManagerGlobal.java:173)
at android.hardware.display.DisplayManagerGlobal$1.recompute(DisplayManagerGlobal.java:169)
at android.app.PropertyInvalidatedCache.query(PropertyInvalidatedCache.java:999)
at android.hardware.display.DisplayManagerGlobal.getDisplayInfoLocked(DisplayManagerGlobal.java:235)
at android.hardware.display.DisplayManagerGlobal.handleDisplayEvent(DisplayManagerGlobal.java:536)
at android.hardware.display.DisplayManagerGlobal.-$$Nest$mhandleDisplayEvent(Unknown Source:0)
at android.hardware.display.DisplayManagerGlobal$DisplayManagerCallback.onDisplayEvent(DisplayManagerGlobal.java:1370)
at android.hardware.display.IDisplayManagerCallback$Stub.onTransact(IDisplayManagerCallback.java:87)
at android.os.Binder.execTransactInternal(Binder.java:1520)
at android.os.Binder.execTransact(Binder.java:1453)

[Mohammed-Baqer-null]

Thank you for the detailed report! You're right this appears to be a memory management issue in the IDE when handling large multi-module projects, especially with Kotlin Multiplatform.

Your 16-module project is quite substantial, and the current tooling APIs might not be optimized for this scale. I'll investigate the memory usage patterns and see where we can improve:

In the meantime, you could try:

• Closing other apps to free up more RAM
• Restarting the IDE before working on this large project

I'll prioritize looking into this. Thanks for the stack trace - it's very helpful for debugging!

[Rafael2616]

Thanks for the support. I've already tried the previous steps, but the IDE still crashes due to lack of memory. I believe the only solution will be an update.