泄漏 - GeneralBlock-3584 [英] Leak - GeneralBlock-3584

查看:23
本文介绍了泄漏 - GeneralBlock-3584的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我尝试使用 Instruments 检查我的 iPhone 应用程序的泄漏时,一切都很好.实际真实设备上的同一应用程序在应用程序启动期间多次显示此泄漏.这是非常不确定的,它发生在系统库中.我试图在没有运气的情况下搜索解决方案.有人遇到同样的问题吗?有大佬知道解决办法吗?

When i try to check leaks of my iPhone App using Instruments, everything is just fine. Same App on actual real device shows this leak for a few times during the app launch. It is pretty non-deterministic and it happens in system libraries. I tried to google down the solution without a luck. Anyone experiencing the same problems? Anyone knows the solution?

我觉得有趣的是,我在代码中的每一次泄漏迟早都会使应用程序崩溃.这些 GeneralBlock-3584 泄漏使应用程序保持完美稳定.这可能是 AppStore 被拒绝的原因吗?

I find interesting, that every of my leak in code will crash the app sooner or later. These GeneralBlock-3584 leaks keeps app perfectly stable. Might this be reason for AppStore rejection?

感谢您提供有关此未记录问题的任何答案(不幸的是,Apple 保持沉默).

Thanx for any answer regarding this undocumented problem (Apple is silent unfortunately).

推荐答案

泄漏检测工具通常会产生误报,尤其是在底层系统库中.

Leak detection tools can often yield false positives, especially in underlying system libraries.

我熟悉这些泄露"的 GeneralBlocks,根据我的经验,它们并没有导致 App Store 被拒绝.

I am familiar with these "leaked" GeneralBlocks, and they didn't cause an App Store rejection in my experience.

IANAASRW**,但我认为你很好.

IANAASRW**, but I think you're fine.

** 我不是 App Store 审核向导

** I am not an App Store Review Wizard

这篇关于泄漏 - GeneralBlock-3584的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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