Adaptive subdivision crash (computing displacement) and huge memory consumption #100915

New Issue

Niels Farragher · 2022-09-08T14:06:37+02:00

Niels Farragher commented

2022-09-08 14:06:37 +02:00

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: D3D12 (Microsoft Basic Render Driver) Microsoft Corporation 4.2 (Core Profile) Mesa 22.2.0-devel (git-7cbdf9e261)

Blender Version
Broken: version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: bcfdb14560
Worked: (newest version of Blender that worked as expected)

*Short description of error
File crashes before during computation of displacement

Exact steps for others to reproduce the error
On attached file, start a single image render using CPU rendering. Memory usage (according to task manager) will ramp up to 121 Gb during tesselation. During computing of normals memory goes up to around 200 Gb. Crash during computation of displacement (object atelier.234) with exception_access_violation
System has 385 Gb of total memory so at point of crash around 175 Gb of free memory is still available. Note that size of render is only 800x800px

bug_tesselation3.blend

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: D3D12 (Microsoft Basic Render Driver) Microsoft Corporation 4.2 (Core Profile) Mesa 22.2.0-devel (git-7cbdf9e261) **Blender Version** Broken: version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: `bcfdb14560` Worked: (newest version of Blender that worked as expected) **Short description of error* File crashes before during computation of displacement **Exact steps for others to reproduce the error** On attached file, start a single image render using CPU rendering. Memory usage (according to task manager) will ramp up to 121 Gb during tesselation. During computing of normals memory goes up to around 200 Gb. Crash during computation of displacement (object atelier.234) with exception_access_violation System has 385 Gb of total memory so at point of crash around 175 Gb of free memory is still available. Note that size of render is only 800x800px [bug_tesselation3.blend](https://archive.blender.org/developer/F13468776/bug_tesselation3.blend)

Niels Farragher commented

2022-09-08 14:06:37 +02:00

Added subscriber: @Nielsf

Germano Cavalcante commented

2022-09-09 01:13:57 +02:00

Added subscribers: @brecht, @mano-wii

Germano Cavalcante commented

2022-09-09 01:13:57 +02:00

It looks like the same problem reported in #73564 (Adaptive subdivision modifier takes to much memory )

In #73564#867093, @brecht wrote:
Adaptive subdivision is not properly working yet in 2.80, and will subdivide the mesh both in Blender and Cycles. This is a known issue, one of the reasons it is still an experimental feature.

It looks like the same problem reported in #73564 (Adaptive subdivision modifier takes to much memory ) > In #73564#867093, @brecht wrote: > Adaptive subdivision is not properly working yet in 2.80, and will subdivide the mesh both in Blender and Cycles. This is a known issue, one of the reasons it is still an experimental feature.

Omar Emara commented

2022-09-13 13:57:40 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-09-13 13:57:40 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Omar Emara commented

2022-09-13 13:57:40 +02:00

What Dicing Rate do you have set in the subdivision options? Does increasing the Dicing rate fixes the issue?

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, 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).

What Dicing Rate do you have set in the subdivision options? Does increasing the Dicing rate fixes the issue? 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, 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)

Niels Farragher commented

2022-09-14 16:28:56 +02:00

Dicing rate is default of 1.0
I increased the dicing rate to 1.5 but same issue. Log files attached are using dicing rate=1.5

bug_tesselation.crash.txt

blender_system_info.txt

blender_debug_output.txt

Dicing rate is default of 1.0 I increased the dicing rate to 1.5 but same issue. Log files attached are using dicing rate=1.5 [bug_tesselation.crash.txt](https://archive.blender.org/developer/F13492398/bug_tesselation.crash.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13492405/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F13492406/blender_debug_output.txt)

Omar Emara commented

2022-09-14 16:48:02 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Germano Cavalcante commented

2022-09-15 14:55:07 +02:00

In my case it doesn't crash, but it doesn't render either:

Malloc returns null: len=139069456 in Cycles Aligned Alloc, total 947739392
Error: run out of memory!
Error: Out of memory

I noticed that importing the file in 2.79 the rendering works.

So, in fact, it is a duplicate of #73564 (Since the problem is mentioned it occurs from 2.80)

In my case it doesn't crash, but it doesn't render either: ``` Malloc returns null: len=139069456 in Cycles Aligned Alloc, total 947739392 Error: run out of memory! Error: Out of memory ``` I noticed that importing the file in 2.79 the rendering works. So, in fact, it is a duplicate of #73564 (Since the problem is mentioned it occurs from 2.80)

Germano Cavalcante commented

2022-09-15 14:55:26 +02:00

Closed as duplicate of #73564

Germano Cavalcante closed this issue

2022-09-15 14:55:26 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Adaptive subdivision crash (computing displacement) and huge memory consumption #100915