Regression: Crash due to high memory usage when compiling Eevee shaders on AMD GPUs #99120
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#99120
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
Blender Version
Broken:
80859a6cb2
is the first bad commitWorked: 3.1.2
Short description of error
Whenever I attempt to load a particular file, the memory gets so high that it crashes several programs if not the entire computer. With another file, the memory usage soars to ridiculous heights trying load textures. This happens in Manjaro, Arch, and EndeavorOS. As it turns out, this seems to be exclusive to 3.2, as downgrading to 3.1.2 resolved the issue.
Exact steps for others to reproduce the error
Attached is a .blend file with only nodes that seriously affect memory usage (eevee_memory_bug.blend)
And another containing the original file from where the bug was detected (Earth.blend)
eevee_memory_bug.blend
Earth.blend
Added subscriber: @celticsamurai
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
@celticsamurai hi, can you reproduce this in 3.2 stable version?: https://www.blender.org/download/
Would 3.2.0-3 be the stable version? If so, the issue seems to persist.
Could you upload crash logs then?: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#linux
Loading textures you mean at the time of rendering?
When I'm just posing the scene and I want to see it with the textures, it does this. The main problem is that the memory usage is just far too high and texture loading is taking too long. I even booted Blender through the terminal to see if I could get more details on what was causing the holdup. I would upload crash logs if I had them, but they're now lost, and I don't want to know what will happen to my computer if I attempt to replicate the issue.
Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs User Info'
The crashes are most likely Blender getting killed by the OOM Killer, so I guess you may not necessary find a crash log. If this happens again, you can look at the end of the output of
sudo dmesg
to see if there are any messages about Blender getting killed. Alternatively, if you rebooted, you can look at the end of the output forjournalctl -b -1
.Can you monitor the GPU memory as well and describe the mechanism at which the memory increase happens? Does GPU memory keep increasing until it is full, then host memory starts increasing until it is full, then the crash happens?
Or does the memory increase merely concern host memory?
Can you reset to factory settings before opening the file to see if a difference in a preference is causing this? File > Defaults > Load Factory Settings.
The OS is capable of handing such cases gracefully, that's why it kills Blender in the first place, so I wouldn't worry too much about it.
The GPU memory seems pretty steady; it's the RAM that seems to gradually increase. I should mention that this only seems to happen when loading a particular set of admittedly complex textures that were made using tons of nodes (but again, Blender didn't used to have a problem loading it swiftly). And yeah the memory just keeps going until it's full, at which point it crashes itself as well as several other programs, and sometimes even the whole computer. Something else worth mentioning is that I have to forcefully shut down Blender when the RAM increase is taking place. Now here's what happened when I tried to CTRL+C the program in the terminal. I invariably have to forcefully terminate the program before it gets worse.
Added subscriber: @rjg
@celticsamurai Could you please check if the issue still occurs when you disable the BlenderKit add-on?
While these textures did come from the media library, disabling it didn't seem to help.
Changed status from 'Needs User Info' to: 'Needs Triage'
Changed status from 'Needs Triage' to: 'Needs User Info'
Not sure if this will help, but does opening blender with
blender --debug-memory
yield any useful messages?Nothing that I can see, but maybe there's something there that you can see?
Changed status from 'Needs User Info' to: 'Needs Triage'
There are no useful messages unfortunately as far as I can see either.
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs User Info'
So any file? Or just the complex ones? Could you share one .blend of the complex ones?
The logs also still show Addons in action, does this also happen when starting blender with the following?
From the media library, the Procedural Earth texture is one that Blender does not seem to like.
Okay. Slightly new development. When running this in Windows, the RAM usage spikes to 40GB, then crashes.
Changed status from 'Needs User Info' to: 'Needs Triage'
Might be related #97591 (Cycles HIP error with image textures on Linux and RDNA1)
Changed status from 'Needs Triage' to: 'Needs User Info'
Is this the Procedural Earth texture file you are talking about? https://www.blenderkit.com/get-blenderkit/7cf8399d-d8b6-42c1-a41f-7390c6f35117/
If permitted, can you attach it here?
@celticsamurai Could you please provide the file / project you were referring to?
All righty. Here it is.Earth.blend
Changed status from 'Needs User Info' to: 'Needs Triage'
Can confirm the
Procedural Earth
shader is really heavy on my machine as well (viweport navigation is really laggy).But not getting crashes or extraordinary memory usage (also not on the GPU)
Added subscriber: @mano-wii
I can confirm excessive RAM consumption by the AMD driver by using the provided file and viewing it in Material Preview mode.
The symbols are not available and the shader is very complex so it is still a little difficult to identify the cause:
The problem doesn't occur in 3.1, so it's a regression.
I'll look for the causing commit and try to simplify the file before confirming.
System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.2.220819
Crashing in 3.2to Regression: Crash due to high memory usage when compiling Eevee shaders on AMD GPUsChanged status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @Jeroen-Bakker
On NVIDIA this doesn't happen, but on AMD it does. this is related to the new way how bump shaders are generated.
The AMD compiler does extensive unrolling which make the compiler use much more memory in the new method.
The change is required in order to develop Eevee-next, but leads to issues when using bump.
This ticket has different symptoms, but same root cause as #98989 (Regression: Eevee bad performance when using procedural bump map.). Close it as duplicate for now.
Closed as duplicate of #98989