Forum Discussion
Hi Atul,
Since It would be a best practice to analyze the host code for possible memory leaks and resolve it. Since you have mentioned that already Valgrind was used to detect the same. If you can share the host code we can have a look at the same.
Thanks and Regards
Anil
Hi Anil,
We were trying with old card and compatible environment but later we tested on SDK RTE 20.2 and design examples on available on Intel site. Hello_world code compiled for emulator device and tested with valgrind tool. When I run host code as it is, it shows:
==2323== LEAK SUMMARY:
==2323== definitely lost: 68,056 bytes in 6 blocks
==2323== indirectly lost: 1,485 bytes in 36 blocks
==2323== possibly lost: 44,570 bytes in 196 blocks
==2323== still reachable: 270,918 bytes in 2,458 blocks
Our OS is CenOS 7 and Valgrind 3.15, observed similar leak on another machine as well. I commented host code and I can see creating context (below line) is showing above memory leak.
context = clCreateContext(NULL, 1, &device, &oclContextCallback, NULL, &status);
Could you check hello_world code your end and let us know your observation,
Thanks,
Atul