Thanks Chris,

unfortunately I can't run it on 64bit since I'm also using 32bit only QTKit 
methods. With instruments, I see some 160 bytes leaks when initing QCRenderers, 
but it seems to be problem a problem with 3rd party CIIFilter, the stack trace 
looks like this all the time:

   0 libsystem_c.dylib calloc
   1 CoreImage sl_value_new_scalar
   2 CoreImage sl_value_base_subst
   3 CoreImage sl_program_reg_unalloc
   4 CoreImage compile_kernels(gsl_parser_struct*, gsl_decl_struct*, void*)
   5 CoreImage gsl_parser_foreach_kernel
   6 CoreImage +[CIKernel kernelsWithString:messageLog:]
   7 CoreImage +[CIKernel kernelsWithString:]
   8 BC Image Unit -[RGBGammaContrastFilter init]
   9 CoreImage -[CIFilter initWithCompatibilityVersion:]
  10 CoreImage +[CIFilter(CIFilterRegistry) 
filterWithName:compatibilityVersion:]
  11 CoreImage +[CIFilter(CIFilterRegistry) filterWithName:]
  12 QuartzComposer +[QCImageFilter isCIFilterCompatible:]
  13 QuartzComposer _RegisterPatches
  14 QuartzComposer +[QCPatch(Registry) patchManager]
  15 QuartzComposer QCPatchFromCompositionWithOptions
  16 QuartzComposer -[QCComposition _makePatch]
  17 QuartzComposer -[QCComposition patch]
  18 QuartzComposer -[QCRenderer 
initWithCGLContext:pixelFormat:colorSpace:composition:]

Anyway, the user rendering in full-hd resolution, so as you mentioned, this 
could be a problem. Is there any method to check the Core Image filters will 
have enough available method to allocate?

Thanks,

Tamas

On May 18, 2013, at 3:38 PM, Chris (CoreGraphics) Wright 
<[email protected]> wrote:

> 
> On May 18, 2013, at 12:25 AM, George Toledo <[email protected]> wrote:
> 
>> On second thought, the the bit about QCPatch(Private) doesn't necessarily 
>> point to a private patch, it's just that _renderAtTime:arguments is listed 
>> in the interface under QCPatch (Private). This is where methods for 
>> execution mode, timebase, enabling/disabling, etc., happen.
>> 
>> I think the com.apple.QuartzComposer points to a built in patch though.
> 
> Right -- com.apple.QuartzComposer means the function being called is in the 
> supplied binary (not a plugin).  (Private) is just a category on the class -- 
> see 
> https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/CustomizingExistingClasses/CustomizingExistingClasses.html
> 
> Most objects have private methods as well that are not API, used for 
> behind-the-scenes work.
> 
> If it's crashing because it can't allocate memory, I'm going to guess that 
> there's a leak somewhere, or lots of large images.  Are you able to run in 
> 64bit?  Leaks take longer to be fatal in 64 bit (though they'll grind the 
> machine into the ground on the way there, so be careful).
> _______________________________________________
> 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/info%40cogevj.hu
> 
> This email sent to [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]

Reply via email to