Segmentation Fault Crashing Blender when Rendering #110415

New Issue

rohan stevenson · 2023-07-24T12:15:44+02:00

rohan stevenson commented

2023-07-24 12:15:44 +02:00

System Information
Operating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03

Blender Version
Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc
Worked: (newest version of Blender that worked as expected)

Short description of error
During rendering, Blender will often crash with segmentation fault "Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header" message.

Exact steps for others to reproduce the error
Need guidance to help provide a blend file to reproduce the issue.

The issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports.

My workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame.

I believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model.

GPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash.

I have tested on 2 other Windows computers with the same results, so it is not Ubuntu related.

Other frames render perfectly.

There is no issue with viewport render mode. Often I get "out of memory", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around.

I have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file.

N.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well.

Is there any advice I can get as to how to narrow down this problem?

**System Information** Operating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03 **Blender Version** Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: `8bda729ef4dc` Worked: (newest version of Blender that worked as expected) **Short description of error** During rendering, Blender will often crash with segmentation fault "Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header" message. **Exact steps for others to reproduce the error** Need guidance to help provide a blend file to reproduce the issue. The issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports. My workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame. I believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model. GPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash. I have tested on 2 other Windows computers with the same results, so it is not Ubuntu related. Other frames render perfectly. There is no issue with viewport render mode. Often I get "out of memory", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around. I have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file. N.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well. Is there any advice I can get as to how to narrow down this problem?

Segmentation Fault 3.5.x.zip

20 KiB

Segmentation Fault 3.6.1.zip

40 KiB

rohan stevenson added the

labels 2023-07-24 12:15:44 +02:00

Iliya Katushenock commented

2023-07-24 14:21:27 +02:00

Hi, thanks for report. Can you attach /home/carillon/Desktop/Blender Workspace/Blender Temporary Files - Clean Regularly/Opera House Scene v2.crash.txt file?
Also, as i can see, you have dependency cycle:

Dependency cycle detected:
  OBMediium Hydraulic Connector.002/TRANSFORM_INIT() depends on
  OBArmature.014/Bone.001/BONE_DONE() via 'Bone Parent'
  OBArmature.014/Bone.001/POSE_IK_SOLVER() via 'IK Solver Result'
  OBLarge Hydraulic.007/TRANSFORM_FINAL() via 'IK'
  OBLarge Hydraulic.007/TRANSFORM_CONSTRAINTS() via 'ObConstraints -> Done'
  OBMediium Hydraulic Connector.002/TRANSFORM_FINAL() via 'Track To'
  OBMediium Hydraulic Connector.002/TRANSFORM_SIMULATION_INIT() via 'Simulation -> Final Transform'
  OBMediium Hydraulic Connector.002/TRANSFORM_EVAL() via 'Transform Eval -> Simulation Init'
  OBMediium Hydraulic Connector.002/TRANSFORM_PARENT() via 'Eval'
  OBMediium Hydraulic Connector.002/TRANSFORM_LOCAL() via 'ObLocal -> ObParent'
  OBMediium Hydraulic Connector.002/TRANSFORM_INIT() via 'Transform Init'
Detected 1 dependency cycles
Dependency cycle detected:
  OBMediium Hydraulic Connector.002/TRANSFORM_INIT() depends on
  OBArmature.014/Bone.001/BONE_DONE() via 'Bone Parent'
  OBArmature.014/Bone.001/POSE_IK_SOLVER() via 'IK Solver Result'
  OBLarge Hydraulic.007/TRANSFORM_FINAL() via 'IK'
  OBLarge Hydraulic.007/TRANSFORM_CONSTRAINTS() via 'ObConstraints -> Done'
  OBMediium Hydraulic Connector.002/TRANSFORM_FINAL() via 'Track To'
  OBMediium Hydraulic Connector.002/TRANSFORM_SIMULATION_INIT() via 'Simulation -> Final Transform'
  OBMediium Hydraulic Connector.002/TRANSFORM_EVAL() via 'Transform Eval -> Simulation Init'
  OBMediium Hydraulic Connector.002/TRANSFORM_PARENT() via 'Eval'
  OBMediium Hydraulic Connector.002/TRANSFORM_LOCAL() via 'ObLocal -> ObParent'
  OBMediium Hydraulic Connector.002/TRANSFORM_INIT() via 'Transform Init'
Detected 1 dependency cycles

Can you fix it and reproduce bug?

Hi, thanks for report. Can you attach `/home/carillon/Desktop/Blender Workspace/Blender Temporary Files - Clean Regularly/Opera House Scene v2.crash.txt` file? Also, as i can see, you have dependency cycle: ``` Dependency cycle detected: OBMediium Hydraulic Connector.002/TRANSFORM_INIT() depends on OBArmature.014/Bone.001/BONE_DONE() via 'Bone Parent' OBArmature.014/Bone.001/POSE_IK_SOLVER() via 'IK Solver Result' OBLarge Hydraulic.007/TRANSFORM_FINAL() via 'IK' OBLarge Hydraulic.007/TRANSFORM_CONSTRAINTS() via 'ObConstraints -> Done' OBMediium Hydraulic Connector.002/TRANSFORM_FINAL() via 'Track To' OBMediium Hydraulic Connector.002/TRANSFORM_SIMULATION_INIT() via 'Simulation -> Final Transform' OBMediium Hydraulic Connector.002/TRANSFORM_EVAL() via 'Transform Eval -> Simulation Init' OBMediium Hydraulic Connector.002/TRANSFORM_PARENT() via 'Eval' OBMediium Hydraulic Connector.002/TRANSFORM_LOCAL() via 'ObLocal -> ObParent' OBMediium Hydraulic Connector.002/TRANSFORM_INIT() via 'Transform Init' Detected 1 dependency cycles Dependency cycle detected: OBMediium Hydraulic Connector.002/TRANSFORM_INIT() depends on OBArmature.014/Bone.001/BONE_DONE() via 'Bone Parent' OBArmature.014/Bone.001/POSE_IK_SOLVER() via 'IK Solver Result' OBLarge Hydraulic.007/TRANSFORM_FINAL() via 'IK' OBLarge Hydraulic.007/TRANSFORM_CONSTRAINTS() via 'ObConstraints -> Done' OBMediium Hydraulic Connector.002/TRANSFORM_FINAL() via 'Track To' OBMediium Hydraulic Connector.002/TRANSFORM_SIMULATION_INIT() via 'Simulation -> Final Transform' OBMediium Hydraulic Connector.002/TRANSFORM_EVAL() via 'Transform Eval -> Simulation Init' OBMediium Hydraulic Connector.002/TRANSFORM_PARENT() via 'Eval' OBMediium Hydraulic Connector.002/TRANSFORM_LOCAL() via 'ObLocal -> ObParent' OBMediium Hydraulic Connector.002/TRANSFORM_INIT() via 'Transform Init' Detected 1 dependency cycles ``` Can you fix it and reproduce bug?

rohan stevenson commented

2023-07-24 15:48:47 +02:00

Update:

I managed to replicate the crash 100% on Linux, Windows, and Mac Silicon using the attached file with just the model I think is responsible for the crashes.

Simply open the file and attempt to render the frame (249). No need for textures.

Update: I managed to replicate the crash 100% on Linux, Windows, and Mac Silicon using the attached file with just the model I think is responsible for the crashes. Simply open the file and attempt to render the frame (249). No need for textures.

Dr I Crashes Blender.zip

86 MiB

rohan stevenson commented

2023-07-24 15:53:13 +02:00

Hi, thanks for report. Can you attach /home/carillon/Desktop/Blender Workspace/Blender Temporary Files - Clean Regularly/Opera House Scene v2.crash.txt file?

The file is included in the second zip file I sent. It was not very informative.

Also, as i can see, you have dependency cycle:

I don't know how to do that. In any case, that is referencing a model that is not causing an issue. I managed to isolate the model that is causing the problem and appended it to a fresh blend file. You can simply open that and attempt to render the frame (249) and Blender will crash. I have tested that on 3 computers. No need for textures.

....NB it is possible to render sub frames. I couldn't render 249.1 or.2, but I could render 248.9

_Hi, thanks for report. Can you attach /home/carillon/Desktop/Blender Workspace/Blender Temporary Files - Clean Regularly/Opera House Scene v2.crash.txt file?_ The file is included in the second zip file I sent. It was not very informative. _Also, as i can see, you have dependency cycle:_ I don't know how to do that. In any case, that is referencing a model that is not causing an issue. I managed to isolate the model that is causing the problem and appended it to a fresh blend file. You can simply open that and attempt to render the frame (249) and Blender will crash. I have tested that on 3 computers. No need for textures. ....NB it is possible to render sub frames. I couldn't render 249.1 or.2, but I could render 248.9

Iliya Katushenock added

and removed

labels 2023-07-24 15:57:45 +02:00

Iliya Katushenock added