Atmapuri

Tracking down memory leaks with Open CL driver

Discussion created by Atmapuri on Sep 9, 2011
Latest reply on Sep 9, 2011 by bpurnomo

Hi!

Is there some support in the Open CL interface to detect where the memory is leaking? My code verified clean, but I dont see inside the driver. From what I understand only this is being executed:

clEnqueueWriteBuffer

clEnqueueReadBuffer

clEnqueueCopyBuffer

clEnqueueNDRangeKernel


Putting these functions in a tight loop causes a memory leak of about 4GB in 5min. Are there some limits on how many times you can reuse a Kernel, mem buffer or other? How could I figure out where is the memory going?

Thanks!
Atmapuri

Outcomes