cocoa bug ? - memory leak in apple example

Discussion in 'Mac Programming' started by Barbus, Oct 31, 2009.

  1. macrumors newbie

    Joined:
    Oct 31, 2009
    #1
    hi all

    please try:
    1 create new application using multi-document template
    2 do nothing, just run this new application using leak-checking instrument
    3 select save-as option - save panel appears ; expand it to show file icons
    4 do nothing, just wait

    result : you'll see memory leak

    also you'll see memory leak in apple's native example ImageApp

    the question: should I ignore such leaks in multi-document application or I did something wrong?

    thanks
     
  2. macrumors 68000

    Joined:
    Jan 28, 2003
    Location:
    Less lost in L.A.
    #2
    If no one replies back saying you did something wrong, then please file this with Apple as a bug.
     
  3. macrumors 68030

    jared_kipe

    Joined:
    Dec 8, 2003
    Location:
    Seattle
    #3
    Every time I launch my application, and sometimes randomly while navigating through my UITabBar I get leaks from CoreGraphics for open_handle_to_dylib_path. Since I'm not doing anything directly with CoreGraphics, and I'm not leaking any UIobjects (that would use coregraphics) I assume its apple's mistake.

    I move on and hope Apple will fix it in the future. But in this case I'm only loosing 128Bytes at a time and it doesn't happen very often.
     
  4. thread starter macrumors newbie

    Joined:
    Oct 31, 2009
    #4
    the caller of the leak I wrote about is :
    -[NSNavFBENode _calculatePreviewThumbnailImageWithMaxSize:isThumbnail:]

    imho it seems like CoreGraphics problem ...
     

Share This Page