Fixed
Status Update
No update yet.
Comments
li...@gmail.com
[Comment deleted]
ch...@google.com
li...@gmail.com
[Comment deleted]
je...@google.com
sp...@google.com
Also of note is the adb error when trying to install bad APK: INSTALL_FAILED_DEXOPT
ra...@google.com
pa...@google.com
pa...@google.com
load dex files over 5Gb. -> load dex files over 5Mb.
li...@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
pa...@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.
pa...@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 (
li...@gmail.com
The option is not documented in --help because it was designed for testing and we're not capable of documenting a reliable way to use it as a workaround of the linearalloc limit.
The linearalloc limit is reached when loading classes. At install time dexopt is loading all classes contained in the dex so it's facing the limit immediately. At execution the limit may be reached after some delay dependending of the usage you have of the packaged classes. If you face it at install time but not at execution, this means you never trigger the loading of some classes. In a real application those never loaded classes should have been shrinked away manually or by Proguard. The exception is when there are different groups of classes in the dex files used in separate process.
About multidex library supported versions I've merged recently a change to try to be clearerhttps://android-review.googlesource.com/#/c/108023/
The summary is that the library should work down to API 4 (Donut), but below ICS applications will probably be hit by the linearalloc limit
The linearalloc limit is reached when loading classes. At install time dexopt is loading all classes contained in the dex so it's facing the limit immediately. At execution the limit may be reached after some delay dependending of the usage you have of the packaged classes. If you face it at install time but not at execution, this means you never trigger the loading of some classes. In a real application those never loaded classes should have been shrinked away manually or by Proguard. The exception is when there are different groups of classes in the dex files used in separate process.
About multidex library supported versions I've merged recently a change to try to be clearer
The summary is that the library should work down to API 4 (Donut), but below ICS applications will probably be hit by the linearalloc limit
sa...@google.com
for Android studio use:
dexOptions {
additionalParameters = ['--multi-dex', '--set-max-idx-number=40000']
}
dexOptions {
additionalParameters = ['--multi-dex', '--set-max-idx-number=40000']
}
sa...@google.com
I still have this issue and it's driving me nuts
pa...@google.com
li...@gmail.com
Comment has been deleted.
li...@gmail.com
I can confirm that the issue is fixed. Updating AGP to 8.0 and lint apis to 31.0.0 helps.
Description
DESCRIBE THE ISSUE IN DETAIL:
STEPS TO REPRODUCE:
./gradlew :app:lintDebugand observe 2 issues;./gradlew :lint-checks:testand observe tests failing.It looks like
PartialResult#mapdoesn't follow the contract in unit tests. It claims to returnLintMapfor the project in context, but under the certain condition it seems to be violated.The conditions require multimodule setup. A
librarymodule must put smth into itsLintMap. Then, when theappmodule accesses its ownLintMapfor the first time it get a map prefilled with the data from thelibrarymodule, instead of the fresh one.To demonstrate the issue I created the following setup:
:appmodule and a:librarymodule;:appmodule containsapp_colorcolor resource, while:librarymodule contains:library_color;colorresource declaration within the module, puts into the partial results and then reports all colors found per module incheckPartialResultsmethod;If you run lint checks using the
./gradlew :app:lintDebugcommand, you'll observe Lint correctly reportingapp_colorfound in:appandlibrary_colorfound in:library. However, if you run the unit tests, you'll observe that Lint also reports alibrary_colorfound in the:app.It looks like while scanning the
:appmodule, the first access to partial results, causesLintCliClientto create new instance of results and fill it with results of the dependent module (seeLintCliClient#getPartialResultsmethod). For some reason this is happening only in tests.The replacement of the
getPartialResult.map()method call withgetPartialResult.mapFor(context.project)method call successfully addresses the issue.There's still a chance, that my test is wrong. In this case, would be great to know in which way.
Studio Build: Chipmunk | 2021.2.1 Version of Gradle Plugin: 7.2.1, 7.4.0-alpha08 Version of Gradle: 7.4.2 OS: Mac OS Monteray 12.4