Question

我试图在gradle中为我的项目设置jumboMode，它似乎能够解决以下DexIndexOverflowException：

com.android.dex.DexException：无法将新索引65536合并为非巨型指令！

DexIndexOverflowException：无法将新索引65772合并为非巨型指令！

1）jumboMode选项实际上是在场景背后做什么的？

android {
    ...
    dexOptions {
        jumboMode true
    }

}

2）我也注意到启用multi-dex也可以解决同样的问题，这两种方法之间的正确选择是什么？

android {
    ...
    defaultConfig {
        ...
        multiDexEnabled true
    }
}

Answer 1

＆＃34;巨型＆＃34;意思是＆＃34;和以前一样，但有大量的参考＆＃34;。

DEX文件中的几乎所有内容都以16位值引用（即使字节码显示为16位＆＃34;单位＆＃34;），因此这里只能处理65536个对象（方法或字符串），不再需要。

但是应用程序可以包含更多字符串！如何解决这个限制？ Android的开发人员刚刚添加了新的操作码＆＃34; jumbo＆＃34;后缀，所以你可以用＆＃34; const-string 16_bit_addr＆＃34;来引用字符串。或＆＃34; const-string 32_bit_addr＆＃34;可以参考2 ^ 32项。目前https://source.android.com/devices/tech/dalvik/dalvik-bytecode＆＃34; jumbo＆＃34;后缀仅存在于字符串（const-string / jumbo）中，但在较旧的文档中包含：

#
# Extended-width opcodes
#

op 00ff const-class/jumbo           41c  y type-ref      continue|throw
op 01ff check-cast/jumbo            41c  n type-ref      continue|throw
op 02ff instance-of/jumbo           52c  y type-ref      continue|throw
op 03ff new-instance/jumbo          41c  y type-ref      continue|throw
op 04ff new-array/jumbo             52c  y type-ref      continue|throw
op 05ff filled-new-array/jumbo      5rc  n type-ref      continue|throw
op 06ff iget/jumbo                  52c  y field-ref     continue|throw
op 07ff iget-wide/jumbo             52c  y field-ref     continue|throw
op 08ff iget-object/jumbo           52c  y field-ref     continue|throw
op 09ff iget-boolean/jumbo          52c  y field-ref     continue|throw
op 0aff iget-byte/jumbo             52c  y field-ref     continue|throw
op 0bff iget-char/jumbo             52c  y field-ref     continue|throw
op 0cff iget-short/jumbo            52c  y field-ref     continue|throw
op 0dff iput/jumbo                  52c  n field-ref     continue|throw
op 0eff iput-wide/jumbo             52c  n field-ref     continue|throw
op 0fff iput-object/jumbo           52c  n field-ref     continue|throw
op 10ff iput-boolean/jumbo          52c  n field-ref     continue|throw
op 11ff iput-byte/jumbo             52c  n field-ref     continue|throw
op 12ff iput-char/jumbo             52c  n field-ref     continue|throw
op 13ff iput-short/jumbo            52c  n field-ref     continue|throw
op 14ff sget/jumbo                  41c  y field-ref     continue|throw
op 15ff sget-wide/jumbo             41c  y field-ref     continue|throw
op 16ff sget-object/jumbo           41c  y field-ref     continue|throw
op 17ff sget-boolean/jumbo          41c  y field-ref     continue|throw
op 18ff sget-byte/jumbo             41c  y field-ref     continue|throw
op 19ff sget-char/jumbo             41c  y field-ref     continue|throw
op 1aff sget-short/jumbo            41c  y field-ref     continue|throw
op 1bff sput/jumbo                  41c  n field-ref     continue|throw
op 1cff sput-wide/jumbo             41c  n field-ref     continue|throw
op 1dff sput-object/jumbo           41c  n field-ref     continue|throw
op 1eff sput-boolean/jumbo          41c  n field-ref     continue|throw
op 1fff sput-byte/jumbo             41c  n field-ref     continue|throw
op 20ff sput-char/jumbo             41c  n field-ref     continue|throw
op 21ff sput-short/jumbo            41c  n field-ref     continue|throw
op 22ff invoke-virtual/jumbo        5rc  n method-ref    continue|throw|invoke
op 23ff invoke-super/jumbo          5rc  n method-ref    continue|throw|invoke
op 24ff invoke-direct/jumbo         5rc  n method-ref    continue|throw|invoke
op 25ff invoke-static/jumbo         5rc  n method-ref    continue|throw|invoke
op 26ff invoke-interface/jumbo      5rc  n method-ref    continue|throw|invoke

DexIndexOverflowException：无法将新索引65772合并为非巨型指令！：Jumbo Mode？和/或Multi-Dex？幕后的是什么？

1 个答案: