Skip to content
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

Seg fault on CUDA #172

Closed
elalish opened this issue Aug 2, 2022 · 4 comments · Fixed by #175
Closed

Seg fault on CUDA #172

elalish opened this issue Aug 2, 2022 · 4 comments · Fixed by #175

Comments

@elalish
Copy link
Owner

elalish commented Aug 2, 2022

Ugh, I really wish our CI had a GPU. I just realized I've been neglecting to test on CUDA locally, and honestly I'm not sure for how long. However, today I noticed that Manifold.SmoothSphere gives: for_each: failed to synchronize: cudaErrorIllegalAddress: an illegal memory access was encountered" thrown in the test body. and then Manifold.ManualSmooth seg faults, but just on CUDA.

I went back to #157 and found the same problem there. I'm having some trouble getting things to build before that, probably because I need different flags or something. @pca006132 Can you repro?

@fire
Copy link
Contributor

fire commented Aug 2, 2022

We've been using swift shader at godot engine, but unclear if that's possible.

@pca006132
Copy link
Collaborator

My old laptop have some hardware issues, so I cannot run CUDA tests for now.

I plan to build a PC later this year (at the end of this year, probably) with nvidia graphics card, so perhaps I can setup a build bot or something to run the tests with CUDA.

Compute shader is an entirely different thing comparing with CUDA, and we rely heavily on thrust for implementing GPU algorithms, so I don't think we can use shaders instead.

@pca006132
Copy link
Collaborator

But I can have a look at the build error you encountered. Can you show me the commit hash of the version that you are trying to build?

@elalish
Copy link
Owner Author

elalish commented Aug 3, 2022

Thanks, but I think it's just my VSCode setup. I'll figure it out (it worked before).

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

Successfully merging a pull request may close this issue.

3 participants