Cycles fails to fill GPU mamory and claims that it is out of memory #46094
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#46094
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
Windows 7 x64
2x GTX 780 TI 3GB
Blender Version
2.74
Short description of error
Cycles says its using 1287 MB of vram but GPU shows 1225 MB being used which means Cycles should be able to put more on the GPU. I know for a fact this happens a lot for me and my friend (Cycles not filling up the cards before quitting)
Here is an Image... for some reason it wont let me drag and drop mine here
Exact steps for others to reproduce the error
Well I dont know if you can unless you have the same GPUs
http://files.derekthe.ninja/attic.blend
Changed status to: 'Open'
Added subscriber: @derekbarker
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
Thanks for the report, but no bug at all here, you are running out of memory. Also, please remember that memory usage reports (especially from Cycles/Blender sides) are only approximations, many different things make it rather imprecise - not to mention the fact that report is not done in real time, while crash will happen immediately when trying to allocate more memory than available…
If you look at the image I linked I used a program to show how much memory was being used on the GPU so you can see the GPU only reaches 1225 MB of vram being used so it isnt that cycles is lying to us, it actually didnt make it to the GPU before it crashed.
Here it is again.
http://files.derekthe.ninja/2015-09-13_01-30-34.png
I still think this is valid..