search

microsoft / OpenCLOn12

The OpenCL-on-D3D12 mapping layer
MIT License
104 stars 13 forks source link

Crash in OpenCLon12.dll when calling clEnqueueNDRangeKernel() #48

Open jfitz-adobe opened 9 months ago

jfitz-adobe commented 9 months ago

hi @jenatali, we're encountering a crash when calling clEnqueueNDRangeKernel(). i have a minidump of the crash that i can make available.

here are the system particulars:

Property Value
OpenCL and OpenGL Compatibility Pack v1.2302.1.0
OS Name Microsoft Windows 11 Pro
Version 10.0.22621 Build 22621
System SKU Surface_Pro_X_1876
Processor Microsoft SQ1 @ 3.0 GHz, 2995 Mhz, 8 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM) 16.0 GB
Adapter Type Adreno 680, Qualcomm Incorporated compatible
Adapter Description Qualcomm(R) Adreno(TM) 680 GPU
Driver Version 27.20.1960.0
INF File oem146.inf (QCDX_Inst.NT section)
shawnhar commented 9 months ago

This looks like an out-of-memory situation. .dumpdebug shows PeakCommitment has reached the process CommitLimit:

BasicPerfInfo AvailablePages : 1,282,410 CommittedPages : 3,147,393 CommitLimit : 4,678,144 PeakCommitment : 4,467,056

I don't see excessive memory usage in the graphics stack here. There is one D3D12 device on the Qualcomm GPU which is using 522 MB, plus a couple of WARP devices which are using negligible amounts of RAM.

How does this memory usage compare to when you run the same scenario in software or on other platforms?

How can we get a repro for the crash?