Re: NSFont leak verified in 10.2
Re: NSFont leak verified in 10.2
- Subject: Re: NSFont leak verified in 10.2
- From: Aki Inoue <email@hidden>
- Date: Mon, 26 Aug 2002 15:22:49 -0700
Chuck,
I assume that this still counts as a bug since there isn't
anyway to release the errant font object, correct?
Yes, it's still a bug.
Aki
On 2002.8.26, at 02:58 PM, Charles Bennett wrote:
Aki Inoue wrote:
Chuck,
In 10.2, we're instantiating separate NSFont instances when the
fontname argument is not valid.
It causes the leak because of the way NSFont instances are cached.
In your case, there is no font named "Arial" in standard Mac OS X
installation.
The argument is supposed to be the font's postscript name.
So, what you need here is "ArialMT" not "Arial"
Aki
Thanks for letting me know.
I assume that this still counts as a bug since there isn't
anyway to release the errant font object, correct?
In 10.1.5 trying to create a font object from a non existant font
returned nil, I beleive.
I wouldn't have caught this but running code in 10.1.5 started leaking
like crazy in 10.2
I just wanted to let others knoow that their code could start leaking
too.
Thanks,
Chuck
--
UPS Management software for OS X
http://www.powerguardian.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.