• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSimage leaking memory or probably just me
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSimage leaking memory or probably just me


  • Subject: Re: NSimage leaking memory or probably just me
  • From: Alexander Cohen <email@hidden>
  • Date: Thu, 28 Sep 2006 16:03:54 -0400

Can you explain better how i would do this. I have all different types of images from which i create NSBitmapImageReps then get their data and save them out. How do i get a NSBitmapImageRep from say, and eps without going through NSImage?

AC

On 28-Sep-06, at 2:55 PM, Bruce Johnson wrote:

I have had the same problem with NSImages, large loops and large
amounts of data.  What I do is create one NSImage and then create
NSBitmapImageReps inside the loop (instead of NSImages) and switch
them in and out of the NSImage (via removeRepresentations and
addRepresentations)  This seems to work.

It is a hassle in that you can't use the convience function of
initWithContentsOfFile:


On 9/28/06, Shawn Erickson <email@hidden> wrote:
On 9/28/06, Alexander Cohen <email@hidden> wrote:
> Hi, i have a large loop that looks like this:
>
>
> for ( i = 0; i < count; i++)
> {
> NSAutoreleasePool* pool = [[NSAutoreleasePool alloc] init];
>
> NSImage* img = [[NSImage alloc] initWithContentsOfFile:self];
> if (!img) {
> [pool release];
> continue;
> }
>
> if (img) [img release];
> img = nil;
>
> [pool release];
> pool = nil;
> }
>
> Every time around the loop, memry is going up drastically and never
> comes down. Am i missing something? Seems to me like the memory
> should stay pretty much the same. ANy ideas?


What "memory" goes up? How are determining that memory usage is increasing?

Also the logic in you loop is rather over kill IMHO...

for ( i = 0;  i < count; i++)
{
    NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];

NSImage *img = [[[NSImage alloc] initWithContentsOfFile:self] autorelease];
if ([img isValid]) { // or just check for not nil ... note a
message to nil is a no-op)
... do your stuff here ...
}


[pool release];
}
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com


This email sent to email@hidden



--
----
Bruce Johnson
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40toomuchspace.com


This email sent to email@hidden



_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Conversion of =E? string (From: malcom <email@hidden>)
 >NSimage leaking memory or probably just me (From: Alexander Cohen <email@hidden>)
 >Re: NSimage leaking memory or probably just me (From: "Shawn Erickson" <email@hidden>)
 >Re: Re: NSimage leaking memory or probably just me (From: "Bruce Johnson" <email@hidden>)

  • Prev by Date: Re: SQL Development
  • Next by Date: Removed view still getting events
  • Previous by thread: Re: Re: NSimage leaking memory or probably just me
  • Next by thread: Re: Conversion of =E? string
  • Index(es):
    • Date
    • Thread