instruments

XCode 5.0.1: can you run automated UI scripts in Instruments?

我的梦境 提交于 2019-12-11 17:34:46
问题 After upgrading to 5.0.1, I'm unable to run UI scripts and get the following message: An error occurred while trying to run the script. Furthermore, recording (the bottom red button) doesn't work either. Is it the only solution to wait for Apple to fix it? Is there a way to downgrade to 5.0? 回答1: i had the same problem, and you should look at this link: https://groups.google.com/forum/#!topic/zucchini-discuss/fQNrfOTaIuU this is what Thomas W. said, and it totally solved my problem: "It is

Xcode-Instruments cannot run app on simulator with the app target I choose

断了今生、忘了曾经 提交于 2019-12-11 14:13:45
问题 I am trying to run an automation on an iOS App using UIAutomation with Instruments. It had worked well when I had tried it out a few weeks back. However, I tried out another automation testing framework (KIF from Square) in the meantime, and now when I try and run Automation with Instruments, it refuses to work. When it had worked, I had carried out the following steps: Open my app in Xcode Run the app Quit the iOS simulator Open Instruments (not necessarily through Xcode, but just by

UIAutomation, UITableView inside UITableViewCell

二次信任 提交于 2019-12-11 11:42:15
问题 I have a horribly coded set of controllers which I am unable to refactor at this time. I need to bring them under automated testing, but have run into an issue with the UIAutomation tool. These controllers are dynamically generated. There were many ways to do this but somebody decided it would be best if they made a tableview containing cells which each contain more tableviews, containing the cells that the user will see and interact with. A simple example of one of these controllers is as

MTKView vs GLKView performance on old devices

痴心易碎 提交于 2019-12-11 11:00:14
问题 I am running into weird performance issues on older device (iPad Mini 2 of year 2014) ever since migrating to MTKView from OpenGLES based views. To summarize, I am rendering live video preview using MTKView and also optionally record videos (like in RosyWriter sample code). My new app version is written in Swift and supports both Metal & OpenGLES. So I have both Open GL and Metal rendering code to compare. I also have a legacy version of app written in Objective C & uses OpenGLES for all

Xcode Instruments - Leaks are shown in the wrong function

℡╲_俬逩灬. 提交于 2019-12-11 10:33:25
问题 My app seems to be leaking some allocations, at least instruments says so, but it points me to the wrong line of code. The stack trace in the image bellow, says that btAllignedAllocDefault is leaking, but it is just a fancy malloc, so the offending line of code must be in initEngine , the problem is that double-ckicling initEngine shows the file containing iniEngine 's definition but always point to some arbitrary line in the first function definition it finds in that file. No mather where I

App / iOS crashes with “Terminating in response to backboardd's termination”

六月ゝ 毕业季﹏ 提交于 2019-12-11 09:39:48
问题 I have an app which is crashing with Terminating in response to backboardd's termination Here the app crashes and even the Springboard. You can see the Apple logo for a short time and it seems that the device is rebooting. This is taken from the device log Incident Identifier: AECC8A4C-B6E0-47B5-A2DD-C3A367107087 CrashReporter Key: 26d2ecafff1bd02c1e774f056b3d20c8b03241c3 Hardware Model: iPad4,2 OS Version: iPhone OS 7.1.2 (11D257) Kernel Version: Darwin Kernel Version 14.0.0: Thu May 15 23

Unknown reason to receive Memory Warning

南楼画角 提交于 2019-12-11 08:28:04
问题 let me come to issue fast. There is no problem in my code so far. My only concern is Memory management. Let me make my app logic clear. When App is launched globally NSmutableDictionary is declared and nearly 300 images are added to that Dictionary with various keys and images are added using pathForResource:ofType method. After my rootViewController loaded my 35 custom UIViews are added to same global dictionary with another key.(this rootViewController will not be used often) I have 4

overall bytes in Xcode Instruments reaches 1 GB is that ok?

冷暖自知 提交于 2019-12-11 07:44:58
问题 Here is my question. I tried to check my allocation part using Instruments in xcode. I am doing some image crop Application using CGImageSourceCreateThumbnailAtIndex for processing the images. while doing the process it is taking to much memory and i released it in right manner. In Instruments the live bytes is 1.56Mb , #living = 22,862 and Overall bytes reaches 1.11Gb after that also it will increase. This application is not working in ipad1. i dont have ipad2 or 3 in hand to test the

Inspecting memory allocation,leaks using Instruments tool

时光怂恿深爱的人放手 提交于 2019-12-11 06:26:30
问题 As suggested by many,instruments tool is the best way to capture the memory allocation and leaks.But for me its been easy to use instruments tool,but i am confused with the detailed results as shown in the above screenshot. Want to know the meaning of following points, 1)All Allocations, 2)Live Bytes, 3)Overall Bytes, 4)Overall. Simple but confusing!Any answer will be greatly appreciated. 回答1: live bytes: The number of bytes that have been allocated but not released yet. Living: *The number

Getting different data in Instruments based on method of profiling

那年仲夏 提交于 2019-12-11 06:02:12
问题 This question is a follow up question to the answer of this: instruments-leaks-and-allocations-tvos The initial question relates to a memory leak I had in a tvOS app, but I think the answer to this question is relevant to iOS/Xcode/Instruments development in general. The issue was solved by removing a closure inside another closure keeping a reference to a variable in the first closure. This caused a retain cycle. Question I really want to understand why I didn't find the issue earlier, let