iOS5“由于太多未处理的消息而丢弃事件0的消息”是什么?意思? [英] iOS5 What does "Discarding message for event 0 because of too many unprocessed messages" mean?

查看:920
本文介绍了iOS5“由于太多未处理的消息而丢弃事件0的消息”是什么?意思?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在对我的应用进行一些性能测试,并注意到运行一些集成需要很长的时间。过了一会儿,我收到了一大堆

 丢弃事件0的消息,因为未处理的消息太多

在xcode控制台。这是什么意思呢?

解决方案

这是Apple技术支持部门对此的支持(支付49美元的开发者技术支持事件后):



这些消息来自Core Location框架。这些消息的最可能原因是在创建CLLocationManager的线程上没有运行循环。 (这意味着在主线程上没有创建CLLocationManager。)正在丢弃的消息是位置消息:事件0是一个位置,事件24是一个授权状态更新。因为正在丢弃的消息,您将不会看到正在调用的适当的委托回调。你设立了地理栅栏还是其他一些回调,并没有足够快的服务?在启动转储事件并记录此消息之前,队列限制似乎为10。
此信息尚未公开记录。我正在与核心位置小组合作,改进报告的讯息,看看能否更好地记录下来。


I'm doing some performance testing of my app and noticed that it takes exceedingly long to run some integrations. After a while, I got a whole bunch of

Discarding message for event 0 because of too many unprocessed messages

in the xcode console. What does this mean precisely?

解决方案

This what Apple Technical Support says about this (after paying $49 for a Developer Tech Support Incident):

These messages are coming from Core Location framework. The most likely cause of these messages is that there isn't a run loop running on the thread on which the CLLocationManager was created. (This implies that the CLLocationManager wasn't created on the main thread.) The messages that are being discarded are location messages: event 0 is a location and event 24 is an authorization status update, for example. Because the messages being discarded, you won't see the appropriate delegate callbacks being invoked. Did you set up a geofence or some other callback and isn't servicing it quickly enough? The queue limit appears to be 10 before it starts dumping events and logging this message. This information isn't publicly documented yet. I'm working with the Core Location team to improve the reported messages and see if this can be better documented.

这篇关于iOS5“由于太多未处理的消息而丢弃事件0的消息”是什么?意思?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆