CL_MEM_OBJECT_ALLOCATION_FAILURE

Good afternoon Forum

Its fairly obvious that CL_MEM_OBJECT_ALLOCATION_FAILURE means that memory can't be allocated.

However, I should like to know why.

Here's the console log from 8.0 build 16.

OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
Loader1 failed to load file "/Volumes/LaCie/guff/FusionTests/Doors/Doors.mov" (clip "/Volumes/LaCie/guff/FusionTests/Doors/Doors.mov" at frame 0) : Invalid argument
Loader1 failed at time 0
Loader1 failed to load file "/Volumes/LaCie/guff/FusionTests/Doors/Doors.mov" (clip "/Volumes/LaCie/guff/FusionTests/Doors/Doors.mov" at frame 0) : Invalid argument
Loader1 failed at time 0
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE
OpenCL clEnqueueNDRangeKernel failed: CL_MEM_OBJECT_ALLOCATION_FAILURE

So there's an invalid argument - suggest frame 0 is corrupt?. The video loads and plays in quicktime.

Any thoughts?

Regards



Andy

You ever figure this one out? I'm getting the same error, but don't really know what is causing it. Thanks.

I found that I could improve stability of Fusion 8 (Windows) be re-encoding quicktimes to exr sequences instead and I am pretty sure that these were the errors I was getting.

I'm getting the error when rendering out still EXR frames from multiple savers. :/ It doesn't seem to affect anything, but it'd still be cool to figure out what it's barking at. Something to do with rendering apparently.

I found that I could improve stability of Fusion 8 (Windows) be re-encoding quicktimes to exr sequences instead and I am pretty sure that these were the errors I was getting.

I have no evidence that Quicktime was the culprit, but I also stopped getting as many CL errors in the console when I stopped using Quicktimes in Loaders -- both on Win10 & OSX (Fu9). I was usually rendering the QTs back out to exr or dpx sequences as an intermediary step in my comps anyway, but just having them loaded (even if not piped to a viewer) seems to have caused those errors to pop up sometimes.