"GPUTexture: texture alloc failed. Likely not enough Video Memory." when rendering an animation with eevee, even on low quality #59351
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#59351
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
Graphics card: R9 280X
system-info.txt
Blender Version
Broken: 2.80 hash
be0c8ed734
Short description of error
Whenever I render out an animation from the attached .blend file using eevee, after 100-150 frames blender will crash with the following error:
This even happens on lower resolutions. My card is a bit older, but it has 3GB of onboard ram and task manager only shows 50% onboard graphics memory being usedwhile rendering. I've had the error on much smaller scenes, but this is the first one I could get it to crash reliably.
Exact steps for others to reproduce the error
Open the following file and press 'F12' to render the entire animation.
Discovery 1.blend
Added subscriber: @brhumphe
I attempted to reproduce this on Mac on hash
f4c70a35a2
, but it did not crash and the animation render was successful. System info: system-info.txtAdded subscriber: @ZedDB
I'll try to render out the animation on my 290x (running linux).
In the mean time, could you try to download the latest AMD drivers? They released a big driver update yesterday I think. So it might be worth trying it out.
No dice, I can render the whole animation and it doesn't crash. Get back to me about the driver situation.
I updated the drivers just to be sure, and it still happens. Must be a Windows thing?
Added subscriber: @fclem
I'm guessing so.
@fclem I don't know what kind of information you want from longer animations like this. Still the attached output of --debug-gpu?
Got a debug build working, and this is the stacktrace I get when it crashes:
The breakpoint is in
cpu_texture.c
line 1291, error "Exception thrown: read access violation. tex was nullptr."Added subscriber: @mano-wii
This is some kind of weird driver bug. It happens to @mano-wii too. I'm thinking I could provide a command line argument to bypass the texture creation test and maybe disable it entirely on certain system.
This issue was referenced by
ba1f178c1c
Changed status from 'Open' to: 'Resolved'