Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Creating context -33 error on windows #38

Open
lebed2045 opened this issue Feb 5, 2021 · 4 comments
Open

Creating context -33 error on windows #38

lebed2045 opened this issue Feb 5, 2021 · 4 comments

Comments

@lebed2045
Copy link

image_2021-02-06_00-41-54

  • sorry for image, I didn't figure out how to copy stuff from the cmd on these windows machines...
@fw-aaron
Copy link

I also get this on Arch Linux. I see you have two GPUs. I do, too. I wonder if it's picking the wrong one...

@fw-aaron
Copy link

Dude, I figured it out...well for me anyway. -33 means "invalid device". You need to figure out which device is invalid and SKIP it. ./profanity.x64 --benchmark -s 1; did it for me because the second device was invalid. My clue that it was invalid is because the name (the part after GPU1: ) was nonsense and it changed each time which tells me it was using uninitialized memory (a bug in the code).

@lebed2045
Copy link
Author

have done that, but now it fails with the same issue as here #51

@fw-aaron
Copy link

I think that's a step up. Congratulations! Progress to #51. I'm guessing that's more of an OpenCL configuration issue.

I don't think this issue should be closed. The application reads from uninitialized memory...bad news.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants