iOS：com.apple.root.default-overcommit-priority [英] iOS: com.apple.root.default-overcommit-priority

问题描述

我收到Crashlytics的崩溃：

I received crash from Crashlytics:

Crashed: com.apple.root.default-overcommit-priority
EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x8b2b0353

Thread : Crashed: com.apple.root.default-overcommit-priority
0  myApplication                  0x0028f0c4 Parse
1  ???                            0xffffffc9 
2  myApplic                       0x00291073 ukeylist_get_scan
3  libsystem_pthread.dylib        0x3aac9c5d _pthread_body + 140
4  libsystem_pthread.dylib        0x3aac9bcf _pthread_start + 102

我的问题：

1. com.apple.root.default -overcommit-priority 是什么意思？ （也许记忆？）


2. 为什么第二行是???


3. 如何解决这个问题？

1. com.apple.root.default-overcommit-priority means? (Maybe memory?)
2. Why second line is ???
3. How to fix this issue?

感谢您抽出宝贵时间帮我解决这个问题。

Thanks for your time to help me solve this issue.

推荐答案

com.apple.root.default-overcommit-priority 是调度队列的名称;我认为这个问题并不重要。

The com.apple.root.default-overcommit-priority is the name of the dispatch queue; I don't think that is anything of importance in this problem.

第二行很有意思，地址非常高。

The second line is interesting, the address being very high.

是 Parse 和 ukeylist_get_scan 您创建或通过库引入的方法？

Is Parse and ukeylist_get_scan methods that you have created or have introduced via a library?

你所拥有的无效内核地址很有趣;它是我希望对代码有效的范围内的地址。通常你会得到一个非常低的值，如崩溃中的0x20（这表明在某处有一个零）。

The invalid kernel address you have is interesting; it is a address in a range I'd expect to be valid for code. Normally you get a really low value such as 0x20 in crashes (which suggests a nil got in somewhere).

我认为你有一些代码用Parse解析一些输入数据方法，但您的代码不能很好地处理意外数据。因此，我建议您在Parse方法上编写更多防御性代码（假设它是您的方法之一），并尝试编写一些传递错误数据的单元测试代码。

I think you have code which parses some input data with a Parse method, but your code is not robust to handle unexpected data. So I recommend you write more defensive code on the Parse method (assuming it is one of your methods), and try writing some unit test code that passes in bad data.

如果这只是一个没有再看到的奇怪问题，那么你无能为力。否则你可以看一下整体模式，看看更多的线索;例如总是相同的设备，或总是某个操作系统版本，或总是低端设备等。

If this is just the odd issue not seen again, there is not much you can do. Otherwise you could just look at the overall pattern to see further clues; e.g. always same device, or always a certain OS version, or always a low-end device, etc.

这篇关于iOS：com.apple.root.default-overcommit-priority的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！