Memory leak on fluid simulation #60062
Labels
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#60062
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10
RAM: 16 GB
Graphics card: NVIDIA Geforce GTX 960m
Blender Version
Broken:
hash:
26d5a3625e
, blender2.8, 2018-11-29Short description of error
The .blend file: water_simulation.blend
Exact steps for others to reproduce the error
Added subscriber: @VitalyEgorov
Memory leak on fluid simulation AND Particle Info node doesn't work on Eeveeto Memory leak on fluid simulationAdded subscriber: @brecht
Please follow the bug submission guidelines:
But particle node support is not a bug, rather a documented limitation:
https://docs.blender.org/manual/en/dev/render/eevee/materials/nodes_support.html#input-nodes
Added subscriber: @ZedDB
Are you sure you are not just running out of RAM? As you said it already take up a lot of RAM (and it is already a bit close to you total 16GB).
It is expected that high resolution fluid sims takes up a lot of ram and is very slow.
Do you get this problem with 2.79?
I tried in blender 2.79b and it took 1 GB for this simulation.
Can you try the 2.79 build from here: https://builder.blender.org/download/ ?
I run out of memory in the latest 2.79 build too.
If you do not, could you provide the 2.79 file?
Changed status from 'Open' to: 'Resolved'
So, I found out that in my simulation there were two objects with ~30000 faces. I tried replace them with spheres and everything worked perfectly. Thanks for help. But I have the question - how many RAM PC mast have for blender working perfectly? 32GB is enough?
So this didn't work in 2.79? If it takes a lot less ram, then you probably have found a problem.
RAM depends on what you are doing. If you really tried, you could do things that go over 32GB. But in most cases, that means that you have gone overkill on something.