Blender 4.1.1 crash when rendering my project #121441

New Issue

Gioxyer · 2024-05-05T13:28:22+02:00

Gioxyer commented

2024-05-05 13:28:22 +02:00

System Information
Operating system: Windows 11 Home
Graphics card: Ryzen 5 5500U with Vega 7 (mobile version)

Blender Version
Broken: (example: 4.1.1, official release, as found on the splash screen)
Worked: /

Short description of error
Basically I try to render the project, but crash, probably it's too heavy for my laptop, but in viewport works correctly

DOWNLOAD LINK REMOVED

Exact steps for others to reproduce the error
Open Blender file
Render Image
Crash

**System Information** Operating system: Windows 11 Home Graphics card: Ryzen 5 5500U with Vega 7 (mobile version) **Blender Version** Broken: (example: 4.1.1, official release, as found on the splash screen) Worked: / **Short description of error** Basically I try to render the project, but crash, probably it's too heavy for my laptop, but in viewport works correctly DOWNLOAD LINK REMOVED **Exact steps for others to reproduce the error** Open Blender file Render Image Crash

blender_debug_output.txt

3.5 KiB

blender_system_info.txt

16 KiB

Gioxyer added the

labels 2024-05-05 13:28:23 +02:00

Gioxyer changed title from ~~Blender 4.1.1 crash when rendering with my project~~ to Blender 4.1.1 crash when rendering my project

2024-05-05 13:28:38 +02:00

Alaska commented

2024-05-05 15:24:54 +02:00

The scene did not crash when I tested it. However the scene does consume a lot of memory when rendering (60GB). So if you don't have enough RAM and page file space, then Blender could crash. However, having crash logs would help identify if this is the case.

Basically I try to render the project, but crash, probably it's too heavy for my laptop, but in viewport works correctly

Assuming memory limits are causing the crash, then why does the viewport work while the final render doesn't?
Because some memory heavy objects are hidden in the viewport, but are visible in the final render. For example:

You have a object called Plane.009. On it is a Mossify geometry nodes setup that's turned off in the viewport, but on in final renders. The mossify geometry nodes setup on this object consumes roughly 4GB of memory due to it using real geometry rather than instances.

You have an object called Plane. It's turned off in the viewport, but on in the final render. It consumes roughly 1GB of memory. I don't think you need this object visible in the render because it appears to be the exact same as another object.

On a side note, I have removed the download link from your report. The .blend file contains assets from the Baga Rain Generator. According to the licensing for this asset, you are not allowed to redistribute it without explicit permission from the original creator. Since you have not shared whether or not you were given explicit permission, I will assume you don't have it and have removed the link.

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
CPU: Ryzen 9 5950X
RAM: 64GB
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86
Blender version: version: 4.1.1, branch: blender-v4.1-release, commit date: 2024-04-15 15:11, hash: e1743a0317bc

The scene did not crash when I tested it. However the scene does consume a lot of memory when rendering (60GB). So if you don't have enough RAM and page file space, then Blender could crash. However, having [crash logs](https://docs.blender.org/manual/en/latest/troubleshooting/crash.html#crash-log) would help identify if this is the case. > Basically I try to render the project, but crash, probably it's too heavy for my laptop, but in viewport works correctly Assuming memory limits are causing the crash, then why does the viewport work while the final render doesn't? Because some memory heavy objects are hidden in the viewport, but are visible in the final render. For example: You have a object called `Plane.009`. On it is a `Mossify` geometry nodes setup that's turned off in the viewport, but on in final renders. The mossify geometry nodes setup on this object consumes roughly 4GB of memory due to it using real geometry rather than instances. You have an object called `Plane`. It's turned off in the viewport, but on in the final render. It consumes roughly 1GB of memory. I don't think you need this object visible in the render because it appears to be the exact same as another object. --- On a side note, I have removed the download link from your report. The .blend file contains assets from the `Baga Rain Generator`. According to the licensing for this asset, you are not allowed to `redistribute it without explicit permission from the original creator`. Since you have not shared whether or not you were given explicit permission, I will assume you don't have it and have removed the link. --- **System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits CPU: Ryzen 9 5950X RAM: 64GB Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86 Blender version: version: 4.1.1, branch: blender-v4.1-release, commit date: 2024-04-15 15:11, hash: `e1743a0317bc`

Alaska added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-05-05 15:25:04 +02:00

Gioxyer commented

2024-05-05 17:25:45 +02:00

I didn't ask for the permission for the addon, so basically I notice with rain cause issue in my case, with mossify and other addon work fine, so basically the problem could be the scene. For the plane I take one for backup as mirror modifier and one applied with all subdivision (to be specific 2 subdivsion surface levels applied).

Gioxyer commented

2024-05-05 17:51:58 +02:00

I notice RAM usage with Blender open consume 99% in viewport, probably by using other elements that I disable on viewport goes out of memory

Viewport v2.png

843 KiB

Viewport v1.png

698 KiB

Viewport v3.png

1.2 MiB

Gioxyer commented

2024-05-05 18:17:48 +02:00

When loading everything as scene, make the last step "Update Mesh Scene" and crash

Now display "Out of memory"

When loading everything as scene, make the last step "Update Mesh Scene" and crash ![image](/attachments/b2b5ebc5-6840-486b-9a6d-a7d2c0e649b3) Now display "Out of memory" ![image](/attachments/93e8af36-d8ab-4b5a-94b4-d7d7332e9e50)

blender_debug_output.txt

28 KiB

blender_system_info.txt

16 KiB

image.png

532 KiB

image.png

771 KiB

Alaska commented

2024-05-06 03:30:42 +02:00

Considering the scene consumers a large amount of RAM, and you're now getting out of memory errors instead of crashing. Then I assume this is just a out of memory issue, which isn't considered a bug. So I will be closing this report.

To get this scene to render, you will either need to reduce the amount of memory it uses (simplify geometry and textures and such. Using command line rendering can also help), or get more memory, or get someone with more memory to render it for you.

Considering the scene consumers a large amount of RAM, and you're now getting out of memory errors instead of crashing. Then I assume this is just a out of memory issue, which isn't considered a bug. So I will be closing this report. To get this scene to render, you will either need to reduce the amount of memory it uses (simplify geometry and textures and such. Using command line rendering can also help), or get more memory, or get someone with more memory to render it for you.

Alaska closed this issue

2024-05-06 03:30:46 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2024-05-06 03:30:47 +02:00

Sign in to join this conversation.