Multiresolution Crashes when applying the 6th subdivision #115952

New Issue

Sven Reinold · 2023-12-08T19:09:12+01:00

Sven Reinold commented

2023-12-08 19:09:12 +01:00

Operating system: Windows 10 64 bit
Intel Core i7 8700K
64GB RAM
Graphics card: Nvidia RTX 3060 12GB

Blender Version
Broken: 3.6.5.
Worked: I don't know, since i made the model in 3.6.5.

Crash when applying the 6th subdivision to the mesh.

I have a model that needs enough details for sculpting. 5 subdivisions are not enough. 18 million polygons are not the amount i need to get skin details. 72 million would be the next step but it crashes halfway. Is 72 million too much for my Graphics card? It sits at 3.6 GB VRAM and 4.2 GB RAM.

Operating system: Windows 10 64 bit Intel Core i7 8700K 64GB RAM Graphics card: Nvidia RTX 3060 12GB **Blender Version** Broken: 3.6.5. Worked: I don't know, since i made the model in 3.6.5. Crash when applying the 6th subdivision to the mesh. I have a model that needs enough details for sculpting. 5 subdivisions are not enough. 18 million polygons are not the amount i need to get skin details. 72 million would be the next step but it crashes halfway. Is 72 million too much for my Graphics card? It sits at 3.6 GB VRAM and 4.2 GB RAM.

LeroySweet_texturing.blend

46 MiB

Sven Reinold added the

labels 2023-12-08 19:09:13 +01:00

Richard Antalik commented

2023-12-08 19:31:32 +01:00

How much RAM do you have? On linux with RTX3060 and 48GB RAM it does not crash, but fails to render mesh... with GPU subdiv disabled I get crash, but probably because system is out of memory.

Sven Reinold commented

2023-12-08 19:39:56 +01:00

How much RAM do you have? On linux with RTX3060 and 48GB RAM it does not crash, but fails to render mesh... with GPU subdiv disabled I get crash, but probably because system is out of memory.

I wrote that i have 64 GB RAM. I monitored my RAM and it went up to 55%.

> How much RAM do you have? On linux with RTX3060 and 48GB RAM it does not crash, but fails to render mesh... with GPU subdiv disabled I get crash, but probably because system is out of memory. I wrote that i have 64 GB RAM. I monitored my RAM and it went up to 55%.

Richard Antalik commented

2023-12-08 21:02:45 +01:00

Unfortunately, that doesn't necessarily tell the full story. At such high subd levels, multiple GB of memory can be allocated at once. In such case OS can say "nope" and Blender just gives up.

In any case, I have tried checking this with debugger and it worked without crash (even though mesh was broken). But this was with 4.1 alpha. Please check if this hapens with alpha build from https://builder.blender.org/download/daily/

Unfortunately, that doesn't necessarily tell the full story. At such high subd levels, multiple GB of memory can be allocated at once. In such case OS can say "nope" and Blender just gives up. In any case, I have tried checking this with debugger and it worked without crash (even though mesh was broken). But this was with 4.1 alpha. Please check if this hapens with alpha build from https://builder.blender.org/download/daily/

Richard Antalik commented

2023-12-08 21:08:43 +01:00

Checked with 3.6, still don't get crash though. Not even sure if this is out of memory issue, since half of the mesh uses only about 20G of memory...

Sven Reinold commented

2023-12-09 11:11:35 +01:00

It's definitely not an out of memory issue. Blender 4.1 alpha closes just like the other versions. The resource monitor show a peak of 56% of 64GB RAM. It's just a closing without a error message.

-I saw that sculpt mode uses less memory so i tried the subdivision there and it worked. I have a 77.5 million mesh with 6.43GiB RAM and 8.4 GiB of VRAM. The problem is the viewport that seems to cause the crash.

It's definitely not an out of memory issue. Blender 4.1 alpha closes just like the other versions. The resource monitor show a peak of 56% of 64GB RAM. It's just a closing without a error message. -I saw that sculpt mode uses less memory so i tried the subdivision there and it worked. I have a 77.5 million mesh with 6.43GiB RAM and 8.4 GiB of VRAM. The problem is the viewport that seems to cause the crash.

Richard Antalik commented

2023-12-09 18:04:27 +01:00

@PratikPB2123 Can you check?

Pratik Borhade commented

2023-12-11 13:20:42 +01:00

Hi, I can confirm the crash with 6 levels of subdivision. Release build did not generate crash info, I'll check debug build

Pratik Borhade commented

2023-12-13 10:30:36 +01:00

In debug mode, I got an exception in nvoglv64.dll(is part of Nvidia drivers). So is it due to GPU subdivision?

In debug mode, I got an exception in `nvoglv64.dll`(is part of Nvidia drivers). So is it due to GPU subdivision?

Pratik Borhade commented

2023-12-13 10:39:21 +01:00

@atdynax , can you check without GPU subdivision? (without GPU subdiv: my system got frozen and had to do restart at 6 levels)

Maybe code profiling tool will help us to identify the problem

@atdynax , can you check without GPU subdivision? (without GPU subdiv: my system got frozen and had to do restart at 6 levels) Maybe code profiling tool will help us to identify the problem

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-12-13 10:42:09 +01:00

Sven Reinold commented

2023-12-13 19:17:41 +01:00

@PratikPB2123 I don't use GPU subdivision. So my problem is without GPU-Subdiv. I had to search for it because i had no idea what it is.

Sven Reinold closed this issue

2023-12-13 19:17:43 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-12-13 19:17:46 +01:00

Sven Reinold reopened this issue

2023-12-13 19:19:08 +01:00

Blender Bot added

and removed

labels 2023-12-13 19:19:10 +01:00

Pratik Borhade commented

2023-12-14 07:01:28 +01:00

Since exception occurred in nvoglv64.dll I would relate it with NVIDIA drivers.
Can you share crash log generated on your device?:

Please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to reproduce the
error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them
to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

Since exception occurred in `nvoglv64.dll` I would relate it with NVIDIA drivers. Can you share crash log generated on your device?: > Please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer).![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-12-14 07:01:38 +01:00

Sven Reinold commented

2023-12-14 10:28:22 +01:00

No description provided.

blender_system_info.txt

26 KiB