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

Segmentation fault during scene rendering with both CUDA and OptiX on Tesla V100 GPUs #1

Open
zhengzhang01 opened this issue Dec 21, 2024 · 2 comments

Comments

@zhengzhang01
Copy link

Description

Running ./render.sh results in a segmentation fault during object synchronization stage, regardless of using CUDA or OptiX as compute device type.

Environment

  • GPU: 8x Tesla V100-SXM2-32GB
  • CPU: Intel Xeon Platinum 8163 @ 2.50GHz
  • Blender: 3.6
  • Python: 3.10

Steps to Reproduce

  1. Clone repository
  2. Run ./render.sh
  3. Crash occurs during object synchronization with error:
Fra:1 Mem:1530.73M (Peak 1695.78M) | Time:00:02.28 | Mem:0.00M, Peak:0.00M | Scene, ViewLayer | Synchronizing object | Cube.001
Fra:1 Mem:1530.74M (Peak 1695.78M) | Time:00:02.28 | Mem:0.00M, Peak:0.00M | Scene, ViewLayer | Synchronizing object | Cube.010
Fra:1 Mem:1530.76M (Peak 1695.78M) | Time:00:02.28 | Mem:0.00M, Peak:0.00M | Scene, ViewLayer | Synchronizing object | object
zsh: segmentation fault (core dumped)

Attempted Fix

Changed device type from OptiX to CUDA in render_scenes_rgbd.py:

bpy.context.preferences.addons["cycles"].preferences.compute_device_type = "CUDA"

But the same segmentation fault persists.

Question

Which files/scripts need to be modified and what changes are needed to successfully run the rendering process without segmentation fault?

@hwjiang1510
Copy link
Owner

Hi,

Thank you for your interest in our work!
Could you try some other random seeds? I found sometimes it reports the segmentation fault randomly.

Best,
Hanwen

@Daniellli
Copy link

Hi, I meet the same problem. And no matter what the seed is, it always comes up with a segmentation fault. Could you further provide more details about your runing environment.

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

No branches or pull requests

3 participants