Mesh to Volume crash on small geometry #105623

New Issue

William B · 2023-03-10T02:58:32+01:00

William B commented

2023-03-10 02:58:32 +01:00

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7

Short description of error
In some cases with small geometries, the Mesh to Volume node ends up consuming a lot of memory and resulting in a crash.

This was identified when running the background rendering script for the attached production file.

With the production file, on the 23rd frame (Every time), I got the crash. It does it from the command line OR from the software itself. From the command line, it shows me the information for the last frame (23), then goes into the error message. I copied it below, and the .crash.txt file is attached.

Current Frame= 23  Axon Length um=60,  n Soma Mito=15,  n Proximal Mito=3,  n MidNeurite Mito=1,  n Distal Mito=3,  Mito Avg LW Ratio=1.33,  Mito Size=0.36,
Error   : UNKNOWN EXCEPTION
Address : 0x00007FFF45F2FE7C
Module  : KERNELBASE.dll
Thread  : 00003638
Writing: C:\Users\Owner\AppData\Local\Temp\NeuroMito 823 03b.crash.txt

Exact steps for others to reproduce the error

Open attached file mesh_to_volume_crash.blend
Reduce the size of primitive geometry to 0.8

Steps for the production file
The .Blend file refers to the attached .CSV file. To run it, you just have to change the folder in the script to wherever you saved the .csv file. I used this command to run it from command line, or just run the script to start the rendering.

"c:\Program Files\Blender Foundation\Blender 3.4\blender.exe" -b "S:\Phys\NeuroMito 823 03b.blend" --python-exit-code 1 --python-text "Render01"

Thank you as always for your work on this amazing program. I am sure it is something about the way I am using geometry nodes or scripting that is causing this.

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: `rB55485cb379f7` **Short description of error** In some cases with small geometries, the `Mesh to Volume` node ends up consuming a lot of memory and resulting in a crash. This was identified when running the background rendering script for the attached production file. With the production file, on the 23rd frame (Every time), I got the crash. It does it from the command line OR from the software itself. From the command line, it shows me the information for the last frame (23), then goes into the error message. I copied it below, and the .crash.txt file is attached. ``` Current Frame= 23 Axon Length um=60, n Soma Mito=15, n Proximal Mito=3, n MidNeurite Mito=1, n Distal Mito=3, Mito Avg LW Ratio=1.33, Mito Size=0.36, Error : UNKNOWN EXCEPTION Address : 0x00007FFF45F2FE7C Module : KERNELBASE.dll Thread : 00003638 Writing: C:\Users\Owner\AppData\Local\Temp\NeuroMito 823 03b.crash.txt ``` **Exact steps for others to reproduce the error** - Open attached file [mesh_to_volume_crash.blend](https://projects.blender.org/attachments/05a0cd82-2195-4f12-9631-b8f897a40289) - Reduce the size of primitive geometry to `0.8` --- **Steps for the production file** The .Blend file refers to the attached .CSV file. To run it, you just have to change the folder in the script to wherever you saved the .csv file. I used this command to run it from command line, or just run the script to start the rendering. "c:\Program Files\Blender Foundation\Blender 3.4\blender.exe" -b "S:\Phys\NeuroMito 823 03b.blend" --python-exit-code 1 --python-text "Render01" Thank you as always for your work on this amazing program. I am sure it is something about the way I am using geometry nodes or scripting that is causing this.

NeuroMito 823 03b.crash.txt

35 KiB

NeuroMito 823 03b.blend

15 MiB

FIV823 03a S01.csv

792 KiB

William B added the

labels 2023-03-10 02:58:33 +01:00

Pratik Borhade changed title from ~~Crash > Error : UNKNOWN EXCEPTION, Address : 0x00007FFF45F2FE7C, Module : KERNELBASE.dll~~ to Crash in KERNELBASE.dll on executing python script

2023-03-10 06:00:39 +01:00

Germano Cavalcante commented

2023-03-10 23:06:19 +01:00

Thanks for the report, but while I can reproduce the crash, the file is still too complex to forward to the developers.

A scenario like this is too time consuming for us to track down, we require the bug reporter to narrow down the problem.

I could notice a high consumption of memory, leading to the crash, but I couldn't identify what caused it.

Can you simplify the file, the script and the steps?

Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

Thanks for the report, but while I can reproduce the crash, the file is still too complex to forward to the developers. A scenario like this is too time consuming for us to track down, we require the bug reporter to narrow down the problem. I could notice a high consumption of memory, leading to the crash, but I couldn't identify what caused it. Can you simplify the file, the script and the steps? Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-03-10 23:06:28 +01:00

William B commented

2023-03-10 23:17:02 +01:00

Got it, I will simplify, see if it re-occurs, then send again. Thank you!

William B commented

2023-03-13 00:16:07 +01:00

Ok, I have drastically simplified (no more script and way less geo nodes and objects), and got it down to a particular pair of values that cause the crash. Now, instead of giving me the Kernell error message, it silently crashes which involves 100% CPU and 100% Memory usage (also crashing the entire computer if you let it build up, but you can shut it down within a few seconds and are the OK).

To reproduce the crash, simply plug in the Mesh to Volume node to the Group Output. Changing the values away from their current pair (27, -0.01) will allow you to connect the geometry without crash. Other values will also crash, these were just the first ones in my sequence to do it. The node tree makes less sense now, and doesn't do anything useful, but it was simplified from the original to try and track it down to something that would give the crash as requested.

It seems that this combination of numbers puts piece of the code into an endless loop that is also filling up memory using all the threads (CPU= 100%).

Thanks for looking into this!

Ok, I have drastically simplified (no more script and way less geo nodes and objects), and got it down to a particular pair of values that cause the crash. Now, instead of giving me the Kernell error message, it silently crashes which involves 100% CPU and 100% Memory usage (also crashing the entire computer if you let it build up, but you can shut it down within a few seconds and are the OK). To reproduce the crash, simply plug in the Mesh to Volume node to the Group Output. Changing the values away from their current pair (27, -0.01) will allow you to connect the geometry without crash. Other values will also crash, these were just the first ones in my sequence to do it. The node tree makes less sense now, and doesn't do anything useful, but it was simplified from the original to try and track it down to something that would give the crash as requested. It seems that this combination of numbers puts piece of the code into an endless loop that is also filling up memory using all the threads (CPU= 100%). Thanks for looking into this!

NeuroMito 823 03b S7.blend

1.5 MiB

Simplified Will crash S7.png

96 KiB

Germano Cavalcante commented

2023-03-13 15:10:40 +01:00

Thanks for simplifying the file, I can confirm the high memory consumption that leads to the crash.

But the Node Group in the .blend file still seems to be overly complex.

The triage team needs to analyze the file to find out if it really is a bug, or if the modifier is forcibly generating heavy geometry that exceeds the memory limits of the hardware. (In this case this is not considered a bug).

I am analyzing the file to try to confirm the bug...

Thanks for simplifying the file, I can confirm the high memory consumption that leads to the crash. But the Node Group in the .blend file still seems to be overly complex. The triage team needs to analyze the file to find out if it really is a bug, or if the modifier is forcibly generating heavy geometry that exceeds the memory limits of the hardware. (In this case this is not considered a bug). I am analyzing the file to try to confirm the bug...

William B commented

2023-03-13 16:12:15 +01:00

The reason I think it may be a bug is because of slightly changing the input values (even in ways which INREASE the heavy geometry) remove the issue. There is no problem at all with slightly different values, but this set of values (as an example) suddenly cause the crash.

Germano Cavalcante commented

2023-03-13 16:33:07 +01:00

I managed to simplify the file.

Apparently the Mesh to Volume node seems to crash with some small meshes.

I'm not familiar enough to determine if this is a bug. In my opinion "open meshes" don't seem like they should be used on this node.

But I will edit the report description and confirm the issue.

I managed to simplify the file. Apparently the `Mesh to Volume` node seems to crash with some small meshes. I'm not familiar enough to determine if this is a bug. In my opinion "open meshes" don't seem like they should be used on this node. But I will edit the report description and confirm the issue.

mesh_to_volume_crash.blend

1.2 MiB

👍 1

Germano Cavalcante changed title from ~~Crash in KERNELBASE.dll on executing python script~~ to Mesh to Volume crash on small geometry

2023-03-13 16:45:50 +01:00

Germano Cavalcante added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Mesh to Volume crash on small geometry #105623