dx with multidex produces dex files that cannot be read at install time on gingerbread devices. [37008143]

Infeasible

Bug

Status Update

No update yet.

Description

kg...@gmail.com

created issue #1

Oct 22, 2014 07:55PM

Please describe the problem in detail, with the following information (if
applicable)
Host OS: OS X
SDK tools version (available in the "About" section of the 'android' tool
UI): 23.0.2
Android Studio version: 0.8.9

STEPS TO REPRODUCE:
1. Build application requiring multiple dex files. Used example found here:

https://github.com/casidiablo/multidex/blob/publishing/README.md
2. Observe app runs correctly on 4.x device.
3. Observe app crashes upon installation on gingerbread device.

EXPECTED RESULTS:
Multidex application runs on gingerbread device.

OBSERVED RESULTS:
Application causes dalvik crash on gingerbread devices:
E/dalvikvm( 2404): LinearAlloc exceeded capacity (8388608), last=6888
E/dalvikvm( 2404): VM aborting
F/libc ( 2404): Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1)
...

ADDITIONAL INFORMATION:
I've seen mentions but no definitive evidence that GB devices cannot load dex files over 5Gb. As an experiment I patched dx to produce smaller dex files (see attachement). Building with the modified dx program produced an APK with smaller (no larger than 3Mb) dex files and installation errors did not occur on gb devices.

Due to this I suspect that dx needs to either by default generate smaller dex files to ensure compatibility with gb devices or be tunable in the build configuration for app producers wishing to maintain compatibility with gb.

dx-smaller-size.patch

839 B

Download

Comments

kg...@gmail.com <kg...@gmail.com> #2Oct 22, 2014 07:57PM

Is this fixed? I'm still seeing this issue with AGP 8.1.0-beta01 + Gradle 8.1

kg...@gmail.com <kg...@gmail.com> #3Oct 22, 2014 07:57PM

The fix has not been landed.

kg...@gmail.com <kg...@gmail.com> #4Oct 22, 2014 07:57PM

Due to this bug in CI we hit configuration cache invalidation 100% of the time. Can we make sure the fix lands soon? And especially before 8.1.0 stable.

xa...@android.com <xa...@android.com> Oct 22, 2014 08:15PM

Assigned to yr...@google.com.

kg...@gmail.com <kg...@gmail.com> #5Oct 22, 2014 08:31PM

I cc'ed you on the CL which should be landed this week.

[Deleted User] <[Deleted User]> #6Oct 22, 2014 08:40PM

Aurimas, is this 8.1 blocking for Androidx? If not, feel free to remove the "Blocking release" label.

yr...@google.com <yr...@google.com> #7Oct 22, 2014 08:46PM

cherry pick to G is landed.

kg...@gmail.com <kg...@gmail.com> #8Oct 22, 2014 09:52PM

This was still broken when running lint, but that is fixed here, which will be included in AGP 8.2.0-alpha10.

TBD if it will be included in 8.1.0 and/or 8.1.1

yr...@google.com <yr...@google.com> #9Oct 23, 2014 08:26AM

Status: Won't Fix (Infeasible)

Reassigning to Xav to review CP to 8.1 branch

ma...@gmail.com <ma...@gmail.com> #10Jun 21, 2017 05:52AM

Scott, do we have a cherry-pick ready for the lint fix?

in...@mobileparadigm.co.uk <in...@mobileparadigm.co.uk> #11Aug 14, 2017 01:56PM

Yes, Change-Id: I994677cebb63de5472bb8ea561bdad0336c72f55

sm...@gmail.com <sm...@gmail.com> #12May 31, 2023 11:29AM

Saurabh, it looks like Xav is OOO until after the deadline for patch 1 check-ins.

Can you or someone else give DrNo approval for ag/I994677cebb63de5472bb8ea561bdad0336c72f55?

sm...@gmail.com <sm...@gmail.com> #13May 31, 2023 11:35AM

Hey Saurabh, ag/I994677cebb63de5472bb8ea561bdad0336c72f55 still needs DrNo approval. Can you give approval, or can you reassign to someone who can?