Blender crash without error message #50734

Closed
opened 2017-02-20 12:56:00 +01:00 by Michael Heidrich · 7 comments

System Information
System 1: Win 10 64x, 16 GB RAM, NVidia GTX 1080
System 2: Win 7 64x, 8 GB RAM, NVidia GTX 1050

Blender Version
Broken: 2.78a e8299c8 and 2.78b (unknown hash)
Worked: None

Short description of error
Files are based on this tutorial: http://blenderdiplom.com/de/tutorials/all-tutorials/617-tutorial-tintentropfen-wasser.html

During bake or animation render process, blender is closing without error message. It seems to have something to do with the complexity of the Scene, the amount of Divisions set for the domain resolution (smoke) and the available RAM since Blender closes at an earlier frame on my Computer at work with 8 GB RAM compared to my Computer at home with 16 GB RAM.
Reducing the amount of divisions seems to help. I can render the attached file "2 drops.blend" with a value of 448 at home and it crashed with 512. At work I have to use 256.

When I added 2 more drops, it now crashes at home at 448. I haven´t found a working value, yet.

Exact steps for others to reproduce the error
You will most likely see the Crash, when you use 4 drops.blend (more complex Scene) and set divisions to max (512) . Then bake.
2 drops.blend
4 drops.blend

**System Information** System 1: Win 10 64x, 16 GB RAM, NVidia GTX 1080 System 2: Win 7 64x, 8 GB RAM, NVidia GTX 1050 **Blender Version** Broken: 2.78a e8299c8 and 2.78b (unknown hash) Worked: None **Short description of error** Files are based on this tutorial: http://blenderdiplom.com/de/tutorials/all-tutorials/617-tutorial-tintentropfen-wasser.html During bake or animation render process, blender is closing without error message. It seems to have something to do with the complexity of the Scene, the amount of Divisions set for the domain resolution (smoke) and the available RAM since Blender closes at an earlier frame on my Computer at work with 8 GB RAM compared to my Computer at home with 16 GB RAM. Reducing the amount of divisions seems to help. I can render the attached file "2 drops.blend" with a value of 448 at home and it crashed with 512. At work I have to use 256. When I added 2 more drops, it now crashes at home at 448. I haven´t found a working value, yet. **Exact steps for others to reproduce the error** You will most likely see the Crash, when you use 4 drops.blend (more complex Scene) and set divisions to max (512) . Then bake. [2 drops.blend](https://archive.blender.org/developer/F491234/2_drops.blend) [4 drops.blend](https://archive.blender.org/developer/F491235/4_drops.blend)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @MickH74

Added subscriber: @MickH74
Member

Added subscriber: @TheOnlyJoey

Added subscriber: @TheOnlyJoey
Member

Looking at the description its a simple out of ram issue.
Some things can get quite out of hand when it comes to ram use.

Try running it with a system monitor and see if it runs against the max, if so, its probably a lack of RAM.

Looking at the description its a simple out of ram issue. Some things can get quite out of hand when it comes to ram use. Try running it with a system monitor and see if it runs against the max, if so, its probably a lack of RAM.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Michael Heidrich self-assigned this 2017-02-21 08:27:45 +01:00

Thanks, Joey.

Yes, RAM use is running against the max and I agree that this is probably a lack of RAM issue.

But shouldn´t there be an error message? I mean at least. Maybe there are even ways of improving Blender to prevent out-of-RAM-issues?
Does Blender use the virtual RAM? If so, can I just increase the amount of virtual RAM to prevent the crash? But currently the OS is managing my virtual RAM and should increase it automatically if needed. Obviously that does not work, so that I assume that the virutal RAM is eiter not used, or not managed properly by the OS or the maximum amount of VM is also reached and cannot be increased any further.

Anyway, I am changing the status to resolved.

Thanks again!
Michael

Thanks, Joey. Yes, RAM use is running against the max and I agree that this is probably a lack of RAM issue. But shouldn´t there be an error message? I mean at least. Maybe there are even ways of improving Blender to prevent out-of-RAM-issues? Does Blender use the virtual RAM? If so, can I just increase the amount of virtual RAM to prevent the crash? But currently the OS is managing my virtual RAM and should increase it automatically if needed. Obviously that does not work, so that I assume that the virutal RAM is eiter not used, or not managed properly by the OS or the maximum amount of VM is also reached and cannot be increased any further. Anyway, I am changing the status to resolved. Thanks again! Michael
Member

No problem.

Managing RAM use is not something easy to do, since it would mean that Blender has to be aware of everything the operating system is doing, which is not the task of a application.
Unfortunately this is a tricky issue.

No problem. Managing RAM use is not something easy to do, since it would mean that Blender has to be aware of everything the operating system is doing, which is not the task of a application. Unfortunately this is a tricky issue.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#50734
No description provided.