Search Results

Search found 3 results on 1 pages for 'user288024'.

Page 1/1 | 1 

  • Cocoa Memory Usage

    - by user288024
    I'm trying to track down some peculiar memory behavior in my Cocoa desktop app. My app does a lot of image processing using NSImage and uploads those images to a website over HTTP using NSURLConnection. After uploading several hundred images (some very large), when I run Instrument I get no leaks. I've also run through MallocDebug and get no leaks. When I dig into object allocations using Instrument I get output like this: GeneralBlock-9437184, Net Bytes 9437184, # Net 1 GeneralBlock-192512, Net Bytes 2695168, # Net 14 and etc., for smaller sizes. When I look at these in detail, they're marked as being owned by 'Foundation' and created via NSConcreteMutableData initWithCapacity. During HTTP upload I'm creating a post body using NSMutableData, so I'm guessing these are buffers Cocoa is caching for me when I create the NSMutableData objects. Is there a way to force Cocoa to free these? I'm 90% positive I'm releasing correctly (and Instruments and MallocDebug seem to confirm this), but I think Cocoa is keeping these around for perf reasons since I'm allocating so many MSMutableData buffers.

    Read the article

  • NSWindowController windowDidLoad not called

    - by user288024
    I have a simple Cocoa app using a NSWindowController subclass. In the nib I have set: File Owner's class to my NSWindowController subclass The 'Window' outlet of the File's Owner to the main NSWindow in the nib. The init method of my NSWindowController subclass is called (I call super), but not matter what I do windowDidLoad is never called. I must be missing something obvious, but for the life of me I can't figure out what it is.

    Read the article

  • XCode File Browsing doesn't open files!

    - by user288024
    Previously when I browsed source code files using Xcode's file browser (located on left side), clicking on a source file would open it in the right window. I must've accidentally changed some setting that stops this behavior -- now single clicking on any file doesn't do anything at all. I'd really like it to go back to the old behavior of opening the file. Any ideas? This behavior is driving me crazy. To open a source file I have to double-click and open in a separate window.

    Read the article

1