I was worrying about it.. I hadn't tried in a device, because this app its on its earlier steps, will have to get a certificate to test it in the device.. Anyway, I guess it wont hurt reporting the bug, ...
mmm.. nice question... where is the link? G On Feb 24, 2010, at 9:54 PM, David Duncan wrote: > On Feb 24, 2010, at 12:44 PM, Gustavo Pizano wrote: > >> when I check with leaks I have the following: >> >> 0 libSystem.B.dylib malloc >> ... >> 14 dyld dlopen >> 15 libSystem.B.dylib dlopen >> 16 CoreGraphics open_handle_to_dylib_path >> 17 CoreGraphics load_function >> 18 CoreGraphics CGLibraryLoadFunction >> 19 CoreGraphics loadBitmapContextDelegateCreator >> ... >> 40 MyApp start > > You didn't execute this code, therefore you have no control over what it > does. Presumably Leaks is attributing this to Core Graphics. The only > reasonable thing you can do about this is to report a bug on it. > > I've also heard it only happens in the simulator, so have you confirmed this > occurs on a device as well? > >> Oh yes Im leaking 128 Bytes. > > > And probably only once. I hate to say "don't worry about it" because it is a > leak and leaks are important, but its only 128 bytes... don't worry about it > :). File a bug with the conditions under which it reproduces and move on. > -- > David Duncan > Apple DTS Animation and Printing > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
