Eevee render out of memory crash #64900
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#64900
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 x64
Graphics card: Nvidia GTX 1060
CPU: Intel i7-6700HQ @ 2.60GHz
RAM: 15.88 GB
Blender Version
Broken: 2.80,
828efef151, 2019-05-20Short description of error
When I hit F12 to render project, the render window appears and after a minute or two, Blender crashes.
Sample .blend file: piles in ground banner design 2-8 v1.blend
Exact steps for others to reproduce the error
Added subscriber: @TravLR
Added subscriber: @Gvgeo-1
Can confirm with win10 amd RX470 gpu 4gb.
Added subscribers: @fclem, @lichtwerk
Also can confirm. Pretty huge output size, getting this reported:
But my 970m has 6BG so that should fit?
@fclem: not sure if this is a bug?
Added subscriber: @StanislavOvcharov
Pretty sure this is a bug, because my small animation project start to crashes when try to render it. Few days ago everything was fine with rendering. It crashes on last three builds. It render several frames from 60 then crash. Win 8.1, gtx 970m
2.80 crashes when attempting to render projectto Eevee render out of memory crash@lichtwerk , yeah I had to set the output dimensions that large because it was going to be for a 32"x97" banner, and most printers want 300dpi or more, so the quality has to be REALLY good.
Added subscriber: @you.le
I don't know if it can help but following this tutorial: http://artificialflight.org/blog/2013/cycles-crash-cuda-tdr-error/ , I managed to render very high quality pictures with EEVEE (even if the tuto concerns cycles). Increasing the timeout delay in regedit on windows might help, I'm not sure though. I think this is more a driver limitation than a blender bug (if increasing the delay solves the issue)
Changed status from 'Confirmed' to: 'Archived'
I don't know any GPU that allows more than 16K textures. I've just added a safety check for render and test if output size is within GPU range.