Paul Kuntke <paulk(a)turmlabor.de> writes:
I hope some here can help me. I'm trying to start openCL-Code
from inside a python multiprocessing worker. Everything woks fine wihh this on my
linux-box. But on my Mac (OS X 10.10.5 Yosemite, python3.6, pyopencl 2018_1) a Error-Box
is popping up, saying my process exited unexpectedly and nothing happens.
OpenCL without or outside multiprocessing seems to work fine as well as multipocessing
without OpenCL uns fine, too. Cl_Buffers can be created. Only compiling CL-Code and
running CL-Kernels does'nt work.
Is anyone experiencing similiar behaviour?
Is it a general limitation to avoid starting opencl-Kernels from multipocessing
Are there any workarounds?
It's hard to help you with that without knowing more detail--OS version,
hardware, CPU/GPU, what specific program are you running (e.g. the
PyOpenCL demos? the test suite?)
Every commit to pyopencl gets tested on Apple hardware, so I'm a little
surprised that you're seeing so much trouble. Here's an example: