Fixed
Status Update
No update yet.
Comments
mi...@gmail.com
[Comment deleted]
cl...@google.com
ma...@gmail.com
Also of note is the adb error when trying to install bad APK: INSTALL_FAILED_DEXOPT
an...@google.com
load dex files over 5Gb. -> load dex files over 5Mb.
mi...@gmail.com
Same here! Looking forward to a solution :)
Android Studio version: 0.8.12
buildToolsVersion 21.0.1
Gradle 1.11
Android Studio version: 0.8.12
buildToolsVersion 21.0.1
Gradle 1.11
an...@google.com
an...@google.com
There is already an option in dx allowing to force generation of smaller dex files:
--set-max-idx-number=<value>
Unfortunately changing the default is not a solution since the linearAlloc limit can be reached at very different levels depending on the classes hierarchy and other criteria.
In addition for most applications, moving to multidex will only help to workaround the linearalloc limit for the installation. But the application will still crash against the same limit at execution. The only working use case where I know multidex can help with linearalloc is when the apk does not contains one application but distinct pieces running in separate process.
--set-max-idx-number=<value>
Unfortunately changing the default is not a solution since the linearAlloc limit can be reached at very different levels depending on the classes hierarchy and other criteria.
In addition for most applications, moving to multidex will only help to workaround the linearalloc limit for the installation. But the application will still crash against the same limit at execution. The only working use case where I know multidex can help with linearalloc is when the apk does not contains one application but distinct pieces running in separate process.
an...@google.com
Thanks for your quick response.
It's nice to know about that command line option. I do not see it in the output of 'dx --help', might be good to add that.
I'm not very familiar with the 'linearAlloc limit' issue outside of the context of the dexopt step. My sample app is able to run once the lower idx value is set, although I do not actually call into any of the library code that is bundled with the app. I assume it's undefined when/if the 'linearAlloc limit' will be hit in a large application on gb.
I'm a bit confused as to the platform compatibility of multidex given the 'linearAlloc limit' bug. What specific versions of Android are supported? The multidex code implies back to v4 (https://android.googlesource.com/platform/frameworks/multidex/+/master/library/src/android/support/multidex/MultiDex.java ) but it would seem that ICS is the earliest supported platform. Is this correct?
It's nice to know about that command line option. I do not see it in the output of 'dx --help', might be good to add that.
I'm not very familiar with the 'linearAlloc limit' issue outside of the context of the dexopt step. My sample app is able to run once the lower idx value is set, although I do not actually call into any of the library code that is bundled with the app. I assume it's undefined when/if the 'linearAlloc limit' will be hit in a large application on gb.
I'm a bit confused as to the platform compatibility of multidex given the 'linearAlloc limit' bug. What specific versions of Android are supported? The multidex code implies back to v4 (
Description
In code when there is occurrence like R.string.sth it is usually folded to ... (3 dots, usually in parenthesis) - like in attached screenshot.
Previously single click or sometimes double click was revealing full definition allowing to edit it. Now it is often stuck and do not expand it. Sometimes it reveals as previously.
Build: AI-241.18034.62.2411.12071903, 202407102313
AS: Koala | 2024.1.1 Patch 1
AI-241.18034.62.2411.12071903, JRE 17.0.11+0--11852314x64 JetBrains s.r.o., OS Windows 10(amd64) v10.0 , screens 2400.0x1350.0, 1920.0x1080.0
Android Gradle Plugin: 8.5.1
Gradle: 8.7
Gradle JDK: Amazon Corretto 21.0.3
NDK: from local.properties: (not specified), latest from SDK: 20.1.5948944
CMake: from local.properties: (not specified), latest from SDK: 3.6.0-rc2, from PATH: (not found)
```