Re: Memory Leaks and ARC

That makes sense. I am now able to see the issue after setting OBJC_DEBUG_MISSING_POOLS=YES. My original code was using CoreFoundation extensively and I introduced Foundation APIs recently. I think this issue got introduced after that. Since this is non-cocoa application (daemon), what I have is ba

Re: Memory Leaks and ARC

On Apr 22, 2014, at 6:49 PM, Jens Alfke wrote: > On Apr 22, 2014, at 6:38 PM, Varun Chandramohan > wrote: >> However when I >> run the same code in older OS 10.7.x and run leaks there I noticed big >> dump of leaks and my daemon (runs without a UI) has numerous _NSCFString >> autoreleased with n

Re: Memory Leaks and ARC

On Apr 22, 2014, at 6:38 PM, Varun Chandramohan wrote: > However when I > run the same code in older OS 10.7.x and run leaks there I noticed big > dump of leaks and my daemon (runs without a UI) has numerous _NSCFString > autoreleased with no pool in place - just leaking - If you’re creating N

Re: Memory Leaks and ARC

Hi Guys, Since we are on the topic I noticed something interesting in my code. My development environment is 10.9.1, and when ever I run ³leaks² command to check for memory leaks I get none. It seems pretty clean. However when I run the same code in older OS 10.7.x and run leaks there I noticed bi

Re: Strange toolbar/view/resize cursor interaction

Ah-ha! This was revealing and disclosed the missing link. Turns out that as expected, the problem was me doing something stupid. In this case, code in a totally different source file was taking these values, much farther down the line, and re-scaling them again. I'd forgotten this old code existed,

Re: Memory Leaks and ARC

On Apr 22, 2014, at 15:18 , Dave wrote: > I assumed that ARC would release myImage on each interation of the loop, > however, this seems not to be the case The ‘myImage’ variable gives up *ownership* of the previous image object when you create a new one in the loop, but whether that leads to

Re: Strange toolbar/view/resize cursor interaction

On Apr 22, 2014, at 15:36 , Eric Shepherd wrote: > When the cursor is at the top edge of my window, the Y value is off by 10 > pixels. > > When the cursor is at the bottom edge of my window, the Y value is off by 40 > pixels. As I suggested previously, this could indicate that your view boun

Re: Memory Leaks and ARC

On Apr 22, 2014, at 4:18 PM, Dave wrote: > This is the main loop of the mainstay of the allocations, it runs this loop > around 650 times loading images of varying sizes: > > myCount = [myURLArray count]; > LogIfDave(@"myURLArray: %@ Count: %i",myURLArray,myCount); > for (myIndex = 0;myIndex <

Re: Strange toolbar/view/resize cursor interaction

So, here's a weird thing I've just now noticed: When the cursor is at the top edge of my window, the Y value is off by 10 pixels. When the cursor is at the bottom edge of my window, the Y value is off by 40 pixels. What the...? Eric Shepherd Gmail: the.she...@gmail.com Twitter: sheppy On Tue,

Memory Leaks and ARC

Hi, I’ve been profiling my App for a while now. I have a test class that reads a lof of data from the server, including downloading images. The test runs on a background thread and is started by clicking a button inside a view controller. Although the test read a lot of data, it does’t retain a

mouse tracking outside a window & dock tracking area

during mouse tracking it is often convenient to register movement outside view bounds. unfortunately, if the cursor is set to other than arrow, movement outside the bottom of a window may enter the dock’s tracking area causing the cursor to change to arrow for the duration of the loop. it is pos

[MEET] Toronto CocoaHeads / tacow - May 13

tacow's next meeting is scheduled for 6:30 PM on Tuesday, May 13, 2014 in meeting room 310 of Metro Hall. Darren Baptiste will be discussing and reviewing AppCode and Reveal.app. For more details and to RSVP, head over to . Thanks, and hope t

Re: Advice for error "NSBundle was released too many times"

On 22 Apr 2014, at 09:10, Colas wrote: > Dear cocoa-dev, > > I have the following error in my application. > Warning: NSBundle NSBundle > (loaded) was released > too many times. For compatibility, it will not be deallocated, but this may > change in the future. Set a breakpoint on __NSBundl

Advice for error "NSBundle was released too many times"

Dear cocoa-dev, I have the following error in my application. Warning: NSBundle NSBundle (loaded) was released too many times. For compatibility, it will not be deallocated, but this may change in the future. Set a breakpoint on __NSBundleOverreleased() to debug It appeared when I added a new