instruments

Robust algorithm for chromatic instrument tuner? [closed]

痴心易碎 提交于 2019-12-02 20:46:27
Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. Who knows the most robust algorithm for a chromatic instrument tuner? I am trying to write an instrument tuner. I have tried the following two algorithms: FFT to create a welch periodogram and then detect the peak frequency A simple autocorrelation ( http://en.wikipedia.org/wiki/Autocorrelation ) I encountered the following basic problems: Accuracy 1: in FFT the relation between samplerate, recording length and bin size

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

淺唱寂寞╮ 提交于 2019-12-02 20:20:27
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 message: Xcode cannot run using the selected device. Choose a destination with a supported architecture in

Do loops and convenience methods cause memory peaks with ARC?

偶尔善良 提交于 2019-12-02 19:33:30
I'm working with ARC and seeing some strange behavior when modifying strings in a loop. In my situation, I'm looping using NSXMLParser delegate callbacks, but I see the same exact behavior and symptoms using a demo project and sample code which simply modifies some NSString objects. You can download the demo project from GitHub , just uncomment one of the four method calls in the main view controller's viewDidLoad method to test the different behaviors. For simplicity's sake, here's a simple loop which I've stuck into an empty single-view application. I pasted this code directly into the

Xcode 6 Memory Leaks Instrument doesn't work

时光怂恿深爱的人放手 提交于 2019-12-02 19:19:01
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? 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 and was marked as duplicate) you can profile your memory leaks using a simulator. This issue seems to occur

Using Xcode Instruments on hackintosh

末鹿安然 提交于 2019-12-02 18:23:46
Using hackintosh (i7-4790K 4GHz, 16GB DDR3, GF980Ti) for developing on Xcode (both Swift and Objective-C) about an year, never get any errors. But now I need to use Instruments apps (such Leaks, Allocations, Energy Log, System Trace, etc.) - but I can not! When I start ANY of these apps I see just transparent window without any visible information. Nax EDIT: as @Eike said in his answer, Instruments and other apps facing this issue work out of the box from 10.13 onwards. For 10.12, the NVWebDriverLibValFix kext is a better/less intrusive fix and avoid some permissions issues. This answer should

Memory leak NSAutoreleasePool

送分小仙女□ 提交于 2019-12-02 17:53:11
问题 With instruments i got a memory leak on this piece of code and i don't understand why! -(void)goToThisUrl:(id) targetUrl { NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init]; if (someCondition) { // Doing some stuff here } // Instruments show memory leak on data else { NSData *data = [NSData dataWithContentsOfURL:[NSURL URLWithString: targetUrl]]; myTargetImage = [UIImage imageWithData:data]; // When releasing data(because data retainCount = 2), i got: // Incorrect decrement of the

How can I get rid of resident dirty memory in Objective-C?

橙三吉。 提交于 2019-12-02 17:10:20
I watched Apple's WWDC 2010 video on Advanced Memory Analysis with Instruments and from that, I was able to find a lot of resident dirty memory. I realize that having so much resident dirty memory is a bad thing (and probably the explanation for my app crashing so much...), but I'm not sure how to fix it. Where should I look? Instruments shows me a lot of potentially useful information that looks like gibberish to me, such as: % of Res Type Resident Size 18% VM_ALLOCATE (8192 pages) 32.00 MB This is in the "Dirty" category - 32 MB of resident dirty memory is a lot on a device that only has 256

Time profiler in instruments is not working

我们两清 提交于 2019-12-02 16:56:09
I recently update my Xcode to version 9.3, so is instruments. After that, time profiler won't work anymore, it usually works fine before. I tried to run it via Xcode, and I tried to run it manually. Doesn't work. The life cycle row stuck in initializing, and I got a bunch of warnings complain about the data volume is too high for a recording mode of "immediate" and some data had to be dropped to move forward . Then I switch to delay mode, still got nothing. Then I create a simple new project, which should have "little data volume", still got nothing. I checked help, I googled, seems like no

Memory leak NSAutoreleasePool

六眼飞鱼酱① 提交于 2019-12-02 10:44:57
With instruments i got a memory leak on this piece of code and i don't understand why! -(void)goToThisUrl:(id) targetUrl { NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init]; if (someCondition) { // Doing some stuff here } // Instruments show memory leak on data else { NSData *data = [NSData dataWithContentsOfURL:[NSURL URLWithString: targetUrl]]; myTargetImage = [UIImage imageWithData:data]; // When releasing data(because data retainCount = 2), i got: // Incorrect decrement of the reference count of an object that is not owned at this point by the caller //[data release]; } [pool

import tuneup.js file not found

别来无恙 提交于 2019-12-02 07:09:26
问题 Using the Xcode iOS Instruments UI Automation tuneup.js javascript library https://github.com/alexvollmer/tuneup_js . I'm having challenges understanding the current working diretory of my launched instrument. I have not been able to make a relative path to the tuneup/tuneup.js script. The destination of the relative path is of course "tuneup/tuneup.js". But what is the starting point? Here's the code: // This works: #import "/Users/mikes/Documents/Full/Path/To/File/Tests/tuneup/tuneup.js" //