instruments

How do you find out what is retaining an object in Instruments?

好久不见. 提交于 2019-12-03 11:33:36
问题 I've recently converted my iOS project over to ARC. One of the view controllers is not calling its dealloc method and is not being dealloc'ed according to Instruments. I've double checked all of my properties and set the appropriate ones to weak. I've also made sure that anything that has the view controller as a delegate has it unset on viewWillDisappear but the view still sticks around in memory. I'm a newbie at Instruments: how can I tell what is retaining this view? 回答1: Well if you are

iOS - i receive memory warnings but have no idea why

守給你的承諾、 提交于 2019-12-03 11:18:59
I am developing for the iOS and checking my app with IPhone and IPad. I receive many memory warnings (didReceiveMemoryWarning is called) but have no idea why. My app is using ~35MB in the peak points, and 4-5 MB when it the lowest point. I tried to find leaks using 'instruments' but could not find any critical issues. Is there a good way to find out why the system sends memory warnings? Memory warning is to be expected in an iOS app. It doesn't have to be because of your app. Other apps are still in memory even if the apps are suspended. The OS will do memory management by sending memory

iOS libsystem_c.dylib strdup memory leak NSZombie not working

一笑奈何 提交于 2019-12-03 09:51:35
问题 Please help me track down an iOS memory leak. Thanks! I'm using xCode 4.0.1 and I tried to activate NSZombie to track a memory leak, but it doesn't seems to work as before, with xCode 3.x I can't find out where the memory leak is coming from, as Instruments points this out: Leaked Object -> GeneralBlock-32 Address -> 0x4c8600 Size -> 32 Bytes Responsible Library -> libsystem_c.dylib Responsible Frame/Caller -> strup At this point I don't know If I'm using Instruments with NSZombie the right

Understanding Instruments memory allocation log on iOS

本秂侑毒 提交于 2019-12-03 09:40:34
问题 I have built an iOS app that is almost done, however, I have recently experienced that it crashes after while due to "Memory pressure". So I started profiling the memory allocations in Instruments and sure, the app does use quite a lot of memory and it only seems to increase during usage. However, relatively new to Instruments memory allocation I am not quite able to decipher where 52 % of the allocations are made, as seen in the screenshot below: It has obviously got something to do with

What is CG Raster Data?

安稳与你 提交于 2019-12-03 09:32:55
I'm trying to find another memory leak in my code, and I can't seem to figure out what CG Raster Data is. While going through the VM Tracker with automatic snapshots enabled, the CG Raster Data seems to be the only part that increases. These also increase steadily without the allocations increasing. I'm not entirely sure what the CG Raster Data is, nor how I would fix it, but at this point the increasing footprint eventually causes a memory error and crash, so it's not good! I do my own text rendering (using CoreText), so I'm thinking that has something to do with it. I also am loading

Instruments > device grayed out

99封情书 提交于 2019-12-03 09:22:53
I'm running an app on my iOS device but, in Instruments, that device is greyed out. This also means I can't attach the process ( Cant launch iOS app with Instruments on device ). Is it anything to do with my earlier question: Instruments > Profile - Revoke and request Xcode: 6.1.1 iOS: 7.1.2 Any idea why? I only had to reboot my phone (not my Mac), and then the error went away (Xcode 9.2, iPhone X running 11.2.6). i was having this issue and resolved it by Unplugging my device Turning my device off Rebooted my mac Turned device back on and plugged into computer after logging back in. now it

skpaymentqueue canmakepayments memory leak checks

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-03 08:17:01
问题 I run Instrument to check Leaks in my app. It got 1 new leaks [SKPaymentQueue canMakePayments] every time start up even no code for payment is called. 回答1: According to this date, SKPaymentQueue's CanMakePayments has memory leak and you can not do anything with it because it's Apple's one. There are lots of tickets opened in Apple's with the same issue. It exists on iOS 10 too. Hope they will fix this issue. ref: https://forums.developer.apple.com/thread/22312 来源: https://stackoverflow.com

Xcode cannot run using the selected device after upgrade to Xcode 5.0

久未见 提交于 2019-12-03 07:36:47
问题 I upgraded to xcode 5.0 today. I then pressed play to run my project in the iOS simulator. This initially worked. Then I decided that I wanted to run the profiler. When I did that, I got the message: Xcode cannot run using the selected device. Choose a destination with a supported architecture in order to run on this device. I looked at a couple past posts on this problem and decided to do a Clean and Build. Now I can no longer run in the profiler or the simulator. I consistently get the

Xcode 6 Memory Leaks Instrument doesn't work

我怕爱的太早我们不能终老 提交于 2019-12-03 06:46:14
问题 I am trying to use Instruments to find leaks within my app. I do it in the same way as I did before updating to Xcode 6.x. Since updating, it won't take any snapshots: the leaks instrument status displays "Analyzing process" and will never change. Both Xcode 6.0.1 and 6.1 GM 2 exhibit this problem. Any workaround? 回答1: Seems like is a bug on iOS8 and not on Xcode. I have Xcode6.1 and the memory leak profiler seems to work on iOS7. As a workaround until Apple fix this (already reported the bug

Xcode Instruments - Zombies - what am I looking for?

帅比萌擦擦* 提交于 2019-12-03 05:56:43
问题 When I run Project/Profile in Xcode and choose " Zombies ", the app runs in the simulator with " NSZombie detection " enabled. But what should I be looking for to tell me that there is a problem? All I see is the Allocation instrument running and the statistics below. Where will it actually show me that a Zombie was detected? 回答1: You will get the leak above the object allocation bar. Check this image; For a reference, check this video 来源: https://stackoverflow.com/questions/12098444/xcode