LinearAlloc 超出容量 (5242880)，last=1092 在我的三星平板设备上安装时出错
我不断地在 logcat 中收到此错误
DexOpt: not resolving ambiguous class 'Lorg/apache/http/client/utils/URLEncodedUtils;'
12-07 05:26:01.085: ERROR/dalvikvm(4620): LinearAlloc exceeded capacity (5242880), last=1092
12-07 05:26:01.085: ERROR/dalvikvm(4620): VM aborting
12-07 05:26:01.187: INFO/DEBUG(2373): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-07 05:26:01.187: INFO/DEBUG(2373): Build fingerprint: 'samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys'
12-07 05:26:01.187: INFO/DEBUG(2373): pid: 4620, tid: 4620 >>> /system/bin/dexopt <<<
12-07 05:26:01.187: INFO/DEBUG(2373): signal 11 (SIGSEGV), fault addr deadd00d
............etc
12-07 05:26:01.347: INFO/dalvikvm(2494): threadid=3: reacting to signal 3
12-07 05:26:01.358: INFO/dalvikvm(2494): Wrote stack traces to '/data/anr/traces.txt'
12-07 05:26:01.551: INFO/dalvikvm(2578): threadid=3: reacting to signal 3
12-07 05:26:02.866: ERROR/dalvikvm(4581): Failed to write stack traces to /data/anr/traces.txt (1370 of 2089): No such file or directory
12-07 05:26:25.976: ERROR/installd(2383): dexopt failed on '/data/dalvik-cache/data@[email protected]@classes.dex' res = 11
12-07 05:26:26.050: WARN/PackageManager(2494): Package couldn't be installed in /data/app/com.check.careerbuilder-1.apk
，并且在控制台中
Installation error: INSTALL_FAILED_DEXOPT
Please check logcat output for more details.
Launch canceled!
我尝试清理项目、重新启动设备、adb 终止并启动服务器，
并且我发现要检查 WipeUserData，但是如何擦除真实设备的用户数据？
如何解决此问题并在三星平板电脑上安装我的 apk？
Am continuously getting, this errors in logcat
DexOpt: not resolving ambiguous class 'Lorg/apache/http/client/utils/URLEncodedUtils;'
12-07 05:26:01.085: ERROR/dalvikvm(4620): LinearAlloc exceeded capacity (5242880), last=1092
12-07 05:26:01.085: ERROR/dalvikvm(4620): VM aborting
12-07 05:26:01.187: INFO/DEBUG(2373): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-07 05:26:01.187: INFO/DEBUG(2373): Build fingerprint: 'samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys'
12-07 05:26:01.187: INFO/DEBUG(2373): pid: 4620, tid: 4620 >>> /system/bin/dexopt <<<
12-07 05:26:01.187: INFO/DEBUG(2373): signal 11 (SIGSEGV), fault addr deadd00d
............etc
12-07 05:26:01.347: INFO/dalvikvm(2494): threadid=3: reacting to signal 3
12-07 05:26:01.358: INFO/dalvikvm(2494): Wrote stack traces to '/data/anr/traces.txt'
12-07 05:26:01.551: INFO/dalvikvm(2578): threadid=3: reacting to signal 3
12-07 05:26:02.866: ERROR/dalvikvm(4581): Failed to write stack traces to /data/anr/traces.txt (1370 of 2089): No such file or directory
12-07 05:26:25.976: ERROR/installd(2383): dexopt failed on '/data/dalvik-cache/data@[email protected]@classes.dex' res = 11
12-07 05:26:26.050: WARN/PackageManager(2494): Package couldn't be installed in /data/app/com.check.careerbuilder-1.apk
and While at Console
Installation error: INSTALL_FAILED_DEXOPT
Please check logcat output for more details.
Launch canceled!
I tried, cleaning the project, restarting device, adb killing and starting server,
and I found WipeUserData to be checked , but how to wipeuserdata for realdevice?
How to resolve this issue and install my apk on samsung tablet?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这是 Dalvik 的一个限制，由异常复杂的接口层次结构触发。
http://code.google.com/p/android/issues/detail ?id=22586
请参阅有关解决方法的详细信息。简单的答案可能是尝试使用不太复杂的不同库。
修复已合并到 Android AOSP 中。
https://android-review.googlesource.com/#/c/30900/
It's a limitation in Dalvik triggered on unusually complex interface hierarchies.
http://code.google.com/p/android/issues/detail?id=22586
See the details for ideas on working around. Simple answer might be to try using different libraries that are less complex.
A fix has been merged into Android AOSP.
https://android-review.googlesource.com/#/c/30900/
一种可能的解决方案是使用 Proguard 删除应用程序中任何未使用的方法/类。
如果您使用库，这可以显着减少应用程序的大小和需要分配的对象数量，从而回避问题（至少达到一定大小的应用程序）。
One potential solution is to use Proguard to trim any unused method/classes from your app.
If you are using libraries this can quite significantly cut down the size of the app and the number of objects that need to be allocated thereby sidestepping the problem (at least up to a certain size app).