-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with OpenCL backend with cpu on macos #88
Comments
Apparently it crashes because, all the kernel variants are rejected because of an invalid group size (to be confirmed). |
i have the same bug, on my MacBook
|
Is this still an issue? |
I get this too on my Mac Pro and MacBook Pro. Tried both the This seems similar to leela-zero/leela-zero#1632 which was fixed in leela-zero/leela-zero#1633
|
I don't think this is an issue. The OpenCL backend cannot use any declared opencl device. There are some minimal requirements. Basically, if the tunning step cannot find any working configuration, this is probably because the device has too low capabilities (small local work size generally). Note that just skipping the tuning step on cpu as suggested simply won't work. We obviously need a working configuration to compile the kernels. Finally, trying to make the OpenCL work on cpu is probably not very productive as the BLAS backend will certainly get much more nps out of the device. |
Is it the same issue here?
|
I am seeing the exact same problem: does this have a known fix by now? |
This issue is most likely a duplicate of #126 and a few others. This is typical: a crash after the search is over. It triggers a thread_local destructor which, in turn, deallocates opencl resources, that triggers crashes on some platforms. This is solved by #516 which was merged into lc0-v0.19.0. I will now close this case. If you feel you have a simular problem, open a new issue, stating everything (platform, lc0 version, steps leading to the crash, etc...). Thanks in advance. |
Trying to use opencl backend with cpu rather than gpu causes a crash after lc0 tries to tune the cpu:
The early versions of lczero did not attempt to tune when cpu was the detected device. Later versions did and crashed in the same way.
The text was updated successfully, but these errors were encountered: