Critical section leaking on a call to clGetPlatformIDs

#1

We’ve been testing our application with Microsoft Application Verifier,
we would like to report that a call to clGetPlatformIDs causes unloading of an active dll (nvopencl64.dll)
whcih still has an active crytical section which it has not freed cauing a leak.

********************* stack trace *****************************
Stack trace for DebugInfo = 0x000001b23b5205f0:

0x00007ff9eb3e0257: ntdll!RtlInitializeCriticalSectionAndSpinCount+0x598F7
0x00007ff9c59f576c: vfbasics!AVrfpInitializeCriticalSectionCommon+0x11C
0x00007ff95a3d2673: nvopencl64!clGetExtensionFunctionAddress+0x3A4D24
0x00007ff95a432554: nvopencl64!clGetExtensionFunctionAddress+0x404C05
0x00007ff95a3c4a1b: nvopencl64!clGetExtensionFunctionAddress+0x3970CC
0x00007ff95a1b9690: nvopencl64!clGetExtensionFunctionAddress+0x18BD41
0x00007ff95a1b7bc1: nvopencl64!clGetExtensionFunctionAddress+0x18A272
0x00007ff95a1b7957: nvopencl64!clGetExtensionFunctionAddress+0x18A008
0x00007ff95a0494b0: nvopencl64!clGetExtensionFunctionAddress+0x1BB61
0x00007ff95a048fb8: nvopencl64!clGetExtensionFunctionAddress+0x1B669
0x00007ff9ac33684c: OpenCL!clEnqueueWriteBufferRect+0x2CD7
0x00007ff9ac3393ce: OpenCL!clEnqueueWriteBufferRect+0x5859
0x00007ff9ac339591: OpenCL!clEnqueueWriteBufferRect+0x5A1C
0x00007ff9ac339082: OpenCL!clEnqueueWriteBufferRect+0x550D
0x00007ff9eb36d58f: ntdll!RtlRunOnceExecuteOnce+0x8F
0x00007ff9e747d1db: KERNELBASE!InitOnceExecuteOnce+0xB
0x00007ff9ac33899c: OpenCL!clEnqueueWriteBufferRect+0x4E27
0x00007ff746c5ca82: GRIDNET_Core!COCLEngine::Initialize+0x2D2
0x00007ff746a823a2: GRIDNET_Core!CBlockchainManager::CBlockchainManager+0x612
0x00007ff746a9895b: GRIDNET_Core!CBlockchainManager::getInstance+0x9B

We would gladly hear out any comments on this and assist with providing more information.

We’ll report this also to NVidia.

With reagrds,
GRIDNET Dev-Team

R

#2

Posting this issue to the following NVidia forum may net you more useful feedback:

Be sure to read the first post in this forum:

#4

We’ll do; thank you for your cooperation