Indeed, the crash is at the same place.
Using the OpenGL Driver Monitor, I can see that the textures graph is
inexorably growing.
Investigating image structures now.
Thank you for heading me in the right direction!
dimitri
On 29 févr. 2012, at 17:51, Christopher Wright wrote:
>> 21 com.apple.QuartzComposer 0x00007fff871ebd90
>> -[QCProvider_CoreImage
>> createTextureBufferForManager:withFormat:target:transformation:bounds:colorSpace:options:]
>> + 1368
>
> ... who in turn was called by QC to create a texture from a CIImage. This is
> a normal operation, but it's possible that textures are leaking. Use OpenGL
> Driver Monitor to look at the number of textures, and see if it grows without
> bound.
On 1 mars 2012, at 18:21, Christopher Wright wrote:
> Hi Dimitri,
>
>> <Quartz Composer_2012-02-27-110318_dimitri-i7.crash>
>
>
> That crash is in the exact same place. So it's probably not a system memory
> leak. It still looks like a GPU resource leak though.
>
> Passing images through JS is relatively dangerous - that might be leaking
> vram/other GPU resources.
>
> --
> Christopher Wright
> [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
