dalvikvm中Android异常
当我在手机上启动应用程序时，我从日志中收到很多以下错误：
E/dalvikvm( 2052): No free temp registers
E/dalvikvm( 2052): Jit: aborting trace compilation, reverting to interpreter
E/dalvikvm( 2052): No free temp registers
E/dalvikvm( 2052): Jit: aborting trace compilation, reverting to interpreter
发生了什么？
When I launch my application on my phone, I get a lot of the following error from the log :
E/dalvikvm( 2052): No free temp registers
E/dalvikvm( 2052): Jit: aborting trace compilation, reverting to interpreter
E/dalvikvm( 2052): No free temp registers
E/dalvikvm( 2052): Jit: aborting trace compilation, reverting to interpreter
what's happened ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Dalvik JIT 使用简单的 &快速寄存器分配器，并且通常不知道如何溢出。在这种情况下，JIT 在编译跟踪时必须用完可用寄存器，它不会尝试溢出，而是放弃跟踪（在某些情况下，它将把跟踪分成两个较小的块并重试）。
这种情况更有可能发生在 Armv5te 系统上，因为 JIT 使用 16 位 Thumb 指令（这限制了有用寄存器的集合）。但是，预计这不会是一个常见问题（并且它应该只会导致性能下降 - 它不应该是正确性问题）。如果您经常看到这种情况发生，请提交错误报告。
谢谢，
...比尔·布兹比
The Dalvik JIT uses a simple & fast register allocator, and generally doesn't know how to spill. In this case, the JIT must have run out of free registers while compiling a trace and rather than attempt to spill, it abandoned the trace (in some cases, it will split the trace in two smaller chunks and retry).
This situation is more likely to occur on an Armv5te system because the JIT uses 16-bit Thumb instructions (which limit the set of useful registers). However, it is not expected to be a common problem (and it should only result is reduced performance - it shouldn't be a correctness issue). If you see this happening frequently, please file a bug report.
Thanks,
...Bill Buzbee
看起来没什么好担心的。来自 Android 问题跟踪器：
http://code.google.com/p/android/issues/detail ?id=18647
“这种情况永远不会发生在实际设备 > armv5te 上，无论如何，这代表着错过了性能机会，而不是正确性问题。我会将 LOGE 更改为 LOGD。”
“该消息的目的是帮助 JIT 开发人员确定特定代码模式的出现频率是否足以证明额外的优化工作是合理的。”
“如果它偶尔发生在较旧的设备（或模拟器）上，那么可以放心地忽略。但是，如果您不断看到它，则表明存在问题 - 可能是配置错误的 Dalvik VM 构建，或者可能已将新代码添加到系统中这使得曾经不常见的情况变得常见。”
Looks like nothing to worry about. From the android issue tracker:
http://code.google.com/p/android/issues/detail?id=18647
"This situation should never occur on an actual device > armv5te, and in any event represents a missed performance opportunity rather than a correctness problem. I'll change the LOGE's to LOGD's."
"The purpose of the message was to help the JIT developers determine whether a particular code pattern occurred frequently enough to justify extra optimization effort."
"If it happens occasionally on an older device (or the emulator) then it's safe to ignore. However, if you're seeing it constantly that suggests a problem - likely a misconfigured Dalvik VM build or perhaps new code has been added to the system that makes what was once an uncommon situation common."