Blender crashes and exits while rendering complex model #63561

New Issue

Fredrik Ingebrigtsen · 2019-04-13T10:07:16+02:00

2019-04-13 10:07:16 +02:00

System Information
Operating system: Windows 10
Graphics card: Nvidia GeForce GTX 1070

Blender Version
Broken: 2.80, 009dbc2bc9, master, 2019-04-09
Worked: (optional)

Short description of error
When I render a big file with house, trees, thuja and a lot of other struf, blender exits without any warnings.

I don't know if it is possible to see the log of why it was crashed as blender exits when it crashes, but when I treied to go to the previous build of blender 2.8 (Hash: f12040e088 - date: 2019-04-05) I was able to render the file using CPU, but not GPU. When I tried GPU, I found this in the info terminal:

bpy.context.scene.cycles.shading_system = True
bpy.context.scene.cycles.shading_system = False
bpy.context.scene.cycles.device = 'GPU'
bpy.data.collections["House_thuia"].hide_render = False
CUDA error: Out of memory in mem_alloc_result, line 850

The attached screenshot is taken during rendering with CPU with *blender 2.8 - Hash: f12040e088b6 - date: 2019-04-05* From the attached image, it seems like Blender needs 28,86 GB of memory if I read the information correct, however my computer only have 16 gb of ram.

I also tried to render the same model with fewer thuias, and then *Blender 2.80, 009dbc2bc9fb, master, 2019-04-09* was able to render, but when tried to use Cryptomatte blender also crashed (see the ticked boxes in image below).

From Cycles settings, Feature Set is "Supported", so I don't use experimental features.

**System Information** Operating system: Windows 10 Graphics card: Nvidia GeForce GTX 1070 **Blender Version** Broken: 2.80, 009dbc2bc9fb, master, 2019-04-09 Worked: (optional) **Short description of error** When I render a big file with house, trees, thuja and a lot of other struf, blender exits without any warnings. I don't know if it is possible to see the log of why it was crashed as blender exits when it crashes, but when I treied to go to the previous build of blender 2.8 (Hash: f12040e088b6 - date: 2019-04-05) I was able to render the file using CPU, but not GPU. When I tried GPU, I found this in the info terminal: bpy.context.scene.cycles.shading_system = True bpy.context.scene.cycles.shading_system = False bpy.context.scene.cycles.device = 'GPU' bpy.data.collections["House_thuia"].hide_render = False CUDA error: Out of memory in mem_alloc_result, line 850 The attached screenshot is taken during rendering with CPU with ``*blender 2.8 - Hash: f12040e088b6 - date: 2019-04-05*`` From the attached image, it seems like Blender needs 28,86 GB of memory if I read the information correct, however my computer only have 16 gb of ram. ![Blender_model.PNG](https://archive.blender.org/developer/F6939096/Blender_model.PNG) I also tried to render the same model with fewer thuias, and then ``*Blender 2.80, 009dbc2bc9fb, master, 2019-04-09*`` was able to render, but when tried to use Cryptomatte blender also crashed (see the ticked boxes in image below). ![image.png](https://archive.blender.org/developer/F6939129/image.png) From Cycles settings, Feature Set is "Supported", so I don't use experimental features.

Fredrik Ingebrigtsen commented

2019-04-13 10:07:16 +02:00

Added subscriber: @fingebrigtsen

Robert Guetzkow commented

2019-04-14 11:45:34 +02:00

Added subscriber: @rjg

Robert Guetzkow commented

2019-04-14 11:45:34 +02:00

As you've said yourself, you're running out of memory. Your project likely needs more memory than Windows allows you to swap to disk, resulting in a crash. If this is the case then there is nothing to fix, you simply don't have enough memory available to render the scene. If you suspect that the crash isn't caused by OOM, you can go to the installation directory and run blender_debug_log.cmd. This will give you a detailed output about what went wrong.

As you've said yourself, you're running out of memory. Your project likely needs more memory than Windows allows you to swap to disk, resulting in a crash. If this is the case then there is nothing to fix, you simply don't have enough memory available to render the scene. If you suspect that the crash isn't caused by OOM, you can go to the installation directory and run `blender_debug_log.cmd`. This will give you a detailed output about what went wrong.

Sebastian Parborg commented

2019-04-14 13:44:32 +02:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-04-14 13:44:32 +02:00

Changed status from 'Open' to: 'Archived'

Sebastian Parborg closed this issue

2019-04-14 13:44:32 +02:00

Sebastian Parborg self-assigned this 2019-04-14 13:44:32 +02:00

Sebastian Parborg commented

2019-04-14 13:44:32 +02:00

As stated, it seems like you simply run out of memory. If you find anything that suggest that the crash isn't because you run out of memory, we can reopen this.

AC commented

2019-04-14 20:04:02 +02:00

Added subscriber: @Tet

AC commented

2019-04-14 20:04:02 +02:00

I've been having this same issue. I'm working on an animation with a linked scene and two linked rigs. It will run/render fine in 2.79.7 but in 2.8 when I render image about 30 seconds will pass while syncing then blender crashes(disappears). My memory appears to be well in acceptable range when this happens. I ran debug log while this happened I don't know where to send it and don't want to post it here because its almost 2000 lines between the two log files.

Last line was in log was: Error : EXCEPTION_ACCESS_VIOLATION

EDIT: Doesn't matter if I render CPU only, GPU only or both

I have this same file in production in 2.79.7 with no issues I figured I'll try 2.8 to see if I could improve render time in cycles.

My setup
Win 10 Pro
32GB RAM
3 SSDs
2x Xeon 2690 v2 (20cores @3GHz)
RTX 2080 ti

I've been having this same issue. I'm working on an animation with a linked scene and two linked rigs. It will run/render fine in 2.79.7 but in 2.8 when I render image about 30 seconds will pass while syncing then blender crashes(disappears). My memory appears to be well in acceptable range when this happens. I ran debug log while this happened I don't know where to send it and don't want to post it here because its almost 2000 lines between the two log files. Last line was in log was: Error : EXCEPTION_ACCESS_VIOLATION EDIT: Doesn't matter if I render CPU only, GPU only or both I have this same file in production in 2.79.7 with no issues I figured I'll try 2.8 to see if I could improve render time in cycles. My setup Win 10 Pro 32GB RAM 3 SSDs 2x Xeon 2690 v2 (20cores @3GHz) RTX 2080 ti

Robert Guetzkow commented

2019-04-14 20:07:31 +02:00

@Tet this seems to be a different problem than the one described here. You can create a bug report here . Files can be attached by drag-and-drop into the browser window.

@Tet this seems to be a different problem than the one described here. You can create a bug report [here ](https://developer.blender.org/maniphest/task/edit/form/1/). Files can be attached by drag-and-drop into the browser window.

Francesc Farfán commented

2019-06-20 01:52:30 +02:00

Added subscriber: @FrancescF

João Victor commented

2020-10-12 17:28:24 +02:00

Added subscriber: @Kazvko

João Victor commented

2020-10-12 17:28:24 +02:00

I have been the same problem, but i couldnt find an aswer for why blender is crashing

blender_system_info.txt

blender_debug_output.txt

I have been the same problem, but i couldnt find an aswer for why blender is crashing [blender_system_info.txt](https://archive.blender.org/developer/F8982899/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8982900/blender_debug_output.txt)

Robert Guetzkow commented

2020-10-12 18:17:43 +02:00

@Kazvko Based on the log files this doesn't seem to be the same issue. Please create a new bug report through Help > Report a Bug in Blender. Please read this guide , it may help you write a bug report that allows us to fix your problem.

We expect all bug reports to follow the submission template . Please provide system information (operating system, GPU, driver version), affected Blender version, previous Blender version that worked properly, a short and precise description of the issue, step by step instructions to reproduce it and, if relevant, a minimal .blend file that showcases the problem. Please also upload the crash log that should be located in C:\Users\[your username]\AppData\Local\Temp\ or %HOMEPATH%\AppData\Local\Temp\.

@Kazvko Based on the log files this doesn't seem to be the same issue. Please create a new bug report through *Help > Report a Bug* in Blender. Please read [this guide ](https://blender.stackexchange.com/questions/1377/best-place-to-put-bug-reports/173685#173685), it may help you write a bug report that allows us to fix your problem. We expect all bug reports to follow the [submission template ](https://developer.blender.org/maniphest/task/edit/form/1/). Please provide **system information** (operating system, GPU, driver version), **affected Blender version**, previous **Blender version that worked properly**, a **short and precise description of the issue**, step by step **instructions to reproduce it** and, if relevant, **a minimal .blend file that showcases the problem**. Please also upload the **crash log** that should be located in `C:\Users\[your username]\AppData\Local\Temp\` or `%HOMEPATH%\AppData\Local\Temp\`.

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

Blender crashes and exits while rendering complex model #63561