WOW it worked!
Thank you very much...
Anyone filed a bug notice of this to Apple?
Thanks to everybody for the suggestions
Stefano
On 12/giu/08, at 11:51, Fabian wrote:
From the archives, originally posted by Rob Keniger:
I had problems with this too, and I use a workaround I found somewhere
On 12.6.2008, at 7:48, Stefano Falda wrote:
On 12/giu/08, at 00:34, Nick Zitzmann wrote:
It's normal for physical memory sizes to go up, and not come down
until either the program is quit or the physical memory is needed
elsewhere. Activity Monitor is not a memory leak detector. If you
w
>From the archives, originally posted by Rob Keniger:
I had problems with this too, and I use a workaround I found somewhere
where you render to a CGImageRef in the context of the current window.
Here's a dump of the code:
//theImage is an existing NSImage
CIImage *outputImage = [CIImage imageWit
On 12/giu/08, at 00:34, Nick Zitzmann wrote:
It's normal for physical memory sizes to go up, and not come down
until either the program is quit or the physical memory is needed
elsewhere. Activity Monitor is not a memory leak detector. If you
want to know where the memory is going, then use
On Jun 11, 2008, at 3:53 PM, Stefano Falda wrote:
I'm working with X-Code3 under Leopard with Garbage Collection ON,
but something seems to go wrong, because at the end of all the
operations the memory is not released (in Activity Monitor there are
>400 MB still active that disappear if I
Hello,
I've got some code similar to the following, in which I loop in a
list of image files and draw their content to another image.
I'm working with X-Code3 under Leopard with Garbage Collection ON, but
something seems to go wrong, because at the end of all the operations
the memory is
