Scene too complex to fit in available memory, with lots of VRAM to spare #57577
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#57577
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
MacOS, Macbook Pro 15" 2017, i7-7700HQ / Radeon Pro 560 4GB
Blender Version
Broken: 2.79b hash
f4dc9f9
Worked: (optional) Latest build on Windows, GTX 1080 Ti
Short description of error
Throws "scene too complex to fit in available memory" before starting the render, whilst only using 700M. On Windows, the per-frame memory usage is 3GB or less, which can fit into the Mac's VRAM.
Exact steps for others to reproduce the error
On MacOS with 4GB graphics card, load blend file, render frames 600 to 800 with valid file destination, using OpenCL GPU Compute engine.
Added subscriber: @MessyMix
Added subscriber: @lichtwerk
Sorry, but it seems the blend file is missing?
marking as incomplete for now
lazyblend.blend
Okay, I thought I attached it the first time around but here it is. Do I have to attach the assets used as well (HDRI, textures)? Or are they embedded in the .blend?
Hi, thx for getting back.
Yes, please pack all into the .blend. You can do so by
File
>External Data
>Pack all into .blend
fastblend.blend
See if this can replicate the problem
OK, blendfile provided
Added subscribers: @Jeroen-Bakker, @ZedDB
@Jeroen-Bakker I leave this for you to decide if it is a driver issue or not.
@MessyMix
Hi, can you try to explain in more detail what this issue is about?
If I read and understand correctly you compare a NVidia driver on Windows to an AMD MacOS driver on Apple.
Different OSes and hardware and drivers lead to other programs and memory usage.
If this is the case the difference is in the driver and hardware.
Thanks in advance.
No problem, not a very major bug at all. It may be an OS-level vRAM allocation issue.
I tried to render a frame on my Mac using the GPU which has 4GB of vram, but it said "scene too complex to fit in available memory". Which is weird, because I expected it should be small enough to fit.
So I checked it by rendering it on a 11GB GTX 1080 Ti, and the scene is only takes up 3GB of vRAM, so it should have been enough to render on the Mac.
Anyways, not a very major issue, so I will see if I can close this. Especially with the new combined CPU/GPU render capability coming up soon.
Changed status from 'Open' to: 'Archived'