Blender Crashes when Cycle rendering in the viewport #107601

New Issue

Stay_Here · 2023-05-04T05:45:38+02:00

Stay_Here commented

2023-05-04 05:45:38 +02:00

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.89

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: ??

Short description of error
Blender Crashes when Cycle rendering in the viewport

Exact steps for others to reproduce the error
In the Sculpt mode, I click the render view, and it crashes. Reports are attached.

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.89 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: ?? **Short description of error** Blender Crashes when Cycle rendering in the viewport **Exact steps for others to reproduce the error** In the Sculpt mode, I click the render view, and it crashes. Reports are attached.

face_6490_6477_forehead inner eyebrow bones refined.crash.txt

75 KiB

blender_debug_output.txt

571 KiB

blender_system_info.txt

24 KiB

Stay_Here added the

labels 2023-05-04 05:45:38 +02:00

YimingWu commented

2023-05-04 06:29:36 +02:00

Hi @Stay_Here , would you please provide us a file that reproduces this crash? Thanks!

Stay_Here commented

2023-05-04 06:46:28 +02:00

@ChengduLittleA The file is not only copyrighted but also too large to provide. Moreover, I can not reproduce the crash. Thanks!

YimingWu commented

2023-05-04 07:12:59 +02:00

@Stay_Here So there's no crash now? If you managed to reproduce the issue, you could provide a trimmed down example file, otherwise we can't really know what's going on.

Stay_Here commented

2023-05-04 07:51:08 +02:00

@ChengduLittleA There are numerous crashes which can not be easily reproduced. That is why Blender Foundation developed the debugging tool to diagnose the cause, and this tool is called "blender_debug_gpu.cmd" located in the Blender's installation directory.

However, you are saying that you don't really know what's going on. This makes me question the usefulness of the debugging tool. Why do they create "blender_debug_gpu.cmd" please? Thanks!

@ChengduLittleA There are numerous crashes which can not be easily reproduced. That is why Blender Foundation developed the debugging tool to diagnose the cause, and this tool is called "blender_debug_gpu.cmd" located in the Blender's installation directory. However, you are saying that you don't really know what's going on. This makes me question the usefulness of the debugging tool. Why do they create "blender_debug_gpu.cmd" please? Thanks!

YimingWu commented

2023-05-04 08:06:08 +02:00

The logging shows some abnormal Invalid clnors in this fan! errors, this could indicate a mesh related problem, whether that's a broken mesh or is it that algorithms failed to handle them would need a file that replicates the issue. That's why it's always recommended to include a file when reporting. The debug log is for pin point the issue in more details. Otherwise we can't really help.

The logging shows some abnormal `Invalid clnors in this fan!` errors, this could indicate a mesh related problem, whether that's a broken mesh or is it that algorithms failed to handle them would need a file that replicates the issue. That's why it's always recommended to include a file when reporting. The debug log is for pin point the issue in more details. Otherwise we can't really help.

Pratik Borhade commented

2023-05-04 08:16:12 +02:00

Hi, thanks for the report.
It'd be difficult to tell what's triggering the crash in your file unless we investigate it locally.
Call stack indicates the crash in function ccl::ImageManager::load_image_metadata. Maybe you're using image files and one of them is corrupted?

Invalid clnors in this fan!

Guess one of the mesh is corrupted. Run mesh.validate and see if that fixes the crash during rendering

import bpy
for obj in bpy.data.objects:
    if obj.type == "MESH" and obj.data is not None:
        if obj.data.validate(verbose=True):
            print(f"Error found: object {obj.name} had invalid mesh data!")

Edit: Ah, had this open for long time. Didn't notice @ChengduLittleA 's last comment

Hi, thanks for the report. It'd be difficult to tell what's triggering the crash in your file unless we investigate it locally. Call stack indicates the crash in function `ccl::ImageManager::load_image_metadata`. Maybe you're using image files and one of them is corrupted? > Invalid clnors in this fan! Guess one of the mesh is corrupted. Run mesh.validate and see if that fixes the crash during rendering ``` import bpy for obj in bpy.data.objects: if obj.type == "MESH" and obj.data is not None: if obj.data.validate(verbose=True): print(f"Error found: object {obj.name} had invalid mesh data!") ``` - - - Edit: Ah, had this open for long time. Didn't notice @ChengduLittleA 's last comment

👍 1

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-05-04 08:17:36 +02:00

Stay_Here commented

2023-05-04 08:17:45 +02:00

@ChengduLittleA Thank you for your explanation, and now I understand what the purpose of "blender_debug_gpu.cmd" is.

I clicked the rendering view for hundreds of time, and only this time it crashes. So the probability to reproduce the crash is smaller than 1/100, which means that reproducing the crash is hard.

@ChengduLittleA Thank you for your explanation, and now I understand what the purpose of "blender_debug_gpu.cmd" is. I clicked the rendering view for hundreds of time, and only this time it crashes. So the probability to reproduce the crash is smaller than 1/100, which means that reproducing the crash is hard.

Stay_Here commented

2023-05-04 08:34:49 +02:00

@PratikPB2123 Hi, I have no idea how to run mesh.validate. Do I just copy and past the code in Blender and click "play" please?

mesh va.jpg

94 KiB

Pratik Borhade commented

2023-05-04 08:45:43 +02:00

Do I just copy and past the code in Blender and click "play" please?

Yes. Once execution is complete, render the scene again.
Also ensure if that script has printed any message in console after execution (Window > Toggle system Console)

> Do I just copy and past the code in Blender and click "play" please? Yes. Once execution is complete, render the scene again. Also ensure if that script has printed any message in console after execution (Window > Toggle system Console)

Stay_Here commented

2023-05-04 10:41:12 +02:00

I ran the script, then rendered the scene, and then ran the script again. During this process, I did not find any error message.

If the mesh has no problem, then maybe it is the one of image files corrupted as you said. I guess that it is one of texture files. But so far all texture images look normal to me.

If you can not find anything meaningful to add, then you can close this quest. Thanks!

I ran the script, then rendered the scene, and then ran the script again. During this process, I did not find any error message. ![run script.jpg](/attachments/f7c320e7-c853-43a1-a0df-bf4a1473bc94) If the mesh has no problem, then maybe it is the one of image files corrupted as you said. I guess that it is one of texture files. But so far all texture images look normal to me. If you can not find anything meaningful to add, then you can close this quest. Thanks!

run script.jpg

653 KiB

Pratik Borhade commented

2023-05-04 10:49:26 +02:00

Thanks.

I ran the script, then rendered the scene.

Did you notice the crash this time? Above script corrects the mesh geometry if its corrupted, see mesh.validate
So crash is less likely to happen if invalid mesh is real culprit.

During this process, I did not find any error message.

I guess you were looking for print messages inside blender console editor.
Instead look at system console: Window > Toggle System console

Thanks. > I ran the script, then rendered the scene. Did you notice the crash this time? Above script corrects the mesh geometry if its corrupted, see [mesh.validate](https://docs.blender.org/api/current/bpy.types.Mesh.html#bpy.types.Mesh.validate) So crash is less likely to happen if invalid mesh is real culprit. > During this process, I did not find any error message. I guess you were looking for print messages inside blender console editor. Instead look at system console: `Window > Toggle System console`

Stay_Here commented

2023-05-04 11:15:58 +02:00

So at this time, I ran the script, then rendered the scene, and then ran the script again. Here are the messages shown on the system console:

At the beginning, the messages shown on the system console are: console-logs.txt

So at this time, I ran the script, then rendered the scene, and then ran the script again. Here are the messages shown on the system console: ![run system console.jpg](/attachments/2fbc4ffb-2046-400d-93d7-ec65c1538212) At the beginning, the messages shown on the system console are: [console-logs.txt](https://projects.blender.org/attachments/b3e438e3-fdd5-45b5-8c7f-2b95c0b9b937)

run system console.jpg

2.1 MiB

console-logs.txt

10 KiB

YimingWu commented

2023-05-04 11:59:13 +02:00

Looks like the mesh is valid hummm...

Pratik Borhade commented

2023-05-04 12:00:31 +02:00

Thanks. Console has not really printed message about invalid geometry.

Did you notice the crash this time (I mean after script execution)?

This is still unanswered.

Edit:

@ChengduLittleA : Looks like the mesh is valid

seems so

Thanks. Console has not really printed message about invalid geometry. > Did you notice the crash this time (I mean after script execution)? This is still unanswered. - - - Edit: > @ChengduLittleA : Looks like the mesh is valid seems so

Stay_Here commented

2023-05-04 20:22:53 +02:00

@PratikPB2123

Did you notice the crash this time (I mean after script execution)?

This is still unanswered.

Before running the script:
I clicked the rendering view for hundreds of time, and only this time it crashes. So the probability to reproduce the crash is smaller than 1/100, which means that reproducing the crash is hard.

After running the script:
Have not found any crash yet.

@PratikPB2123 > Did you notice the crash this time (I mean after script execution)? > > This is still unanswered. Before running the script: I clicked the rendering view for hundreds of time, and only this time it crashes. So the probability to reproduce the crash is smaller than 1/100, which means that reproducing the crash is hard. After running the script: Have not found any crash yet.

Pratik Borhade commented

2023-05-05 11:16:57 +02:00

Thanks for the update.
I think we can close this report considering the crash is occurring occasionally and affected file is not available to us for investigation.
If you find any relevant information which could be related to crash then please feel free to share.
Thanks again for the report!

Thanks for the update. I think we can close this report considering the crash is occurring occasionally and affected file is not available to us for investigation. If you find any relevant information which could be related to crash then please feel free to share. Thanks again for the report!

Pratik Borhade closed this issue

2023-05-05 11:16:59 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-05-05 11:17:00 +02:00

Sign in to join this conversation.