Persistent Data is now shared between F12 renders and viewport rendering (doubles up, leading to out of memory) #107370
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#107370
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-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61
Blender Version
Broken: version: 3.6.0 Alpha, branch: main, commit date: 2023-04-23 19:27, hash:
993d24c1749c
Worked: (newest version of Blender that worked as expected)
Short description of error
I have a scene about 1.7GB in size with 4K textures but renders in 2K using simplify, blender crashes when I open the file > hit F12 and render the scene then close the render windows and switch to render view > it starts compiling then blender closes, in the past it would show out of memory this report:
#105522 (comment)
This issue happens only when persistent Data is active
unfortunately I can't share the file at the moment.
Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]
Could you recreate a file, not necessarily the one used, so we can replicate the problem?
It would also be interesting to identify what in the scene is causing the problem. 4K vs 2k texture, Geometry, GPU vs CPU...
Note that the triage team needs to confirm the issue before forwarding it to the developers. (Showing crash logs to developers directly is only a last resort)
Ill test with another files, I use GPU Cuda, simplify to 2K Textures and persistent data, the main issue I noticed is persistent data, will try to reproduce it in different file though
Poke. Any update?
Unconfirmed issues with no activity for more than a week are closed because, per tracker policy, we assume they are gone.
Still Crashes only when persistent data is On same as before, tested in Cuda
closed by mistake sorry
Need example file so resetting the status.
Hard to guess a possible culprit by looking at the call stack
The issue is that when activating the persistent data, when i hit F12 and render the scene, and the render finishes the VRam is still full, unlike when deactivating the persistent data, the Vram goes down the moment the render finishes, so obviously when the Vram remains full even after render finishes, Blender will crash when switching to render view cuz there are no memory left for it, all is full by previous render, the screen shot shows the vram after rendering the scene with persistent data ON and closing the render window and deleting everything in scene, the Vram is still full
I have an example file it's about 1.5 GB let me know where to upload it. Thank you
even after deleting everything and switching to render view it builds up :D! like 7.7GB used
@mano-wii @PratikPB2123
Here's the file: https://drive.google.com/file/d/1Jq6QY7RgEzk43uIQdPCRKsGAz0NVFQ5x/view?usp=sharing
Steps:
1.Click Render
2.After Render Finishes close render window then switch to render view
-Try both Cuda and Optix
[Blender 3.6] crash when switching from solid to rendered viewto Crash when switching from solid to rendered viewHey @Shady.Hamza, have you still able to reproduce this in last 4.0?
yes unfortunately same everything.
checked both my original file and the one I'm sharing here, both crashed, specially the one shared here after rendering using F12, it gave out of memory, then i closed the render windows and went to render view it crashed
I can confirm having
Persistent Data
ON, this data is not "shared" between F12 and viewport renders, it doubles up.Not sure if this is expected behavior, will confirm for now.
CC @sergey @brecht
Crash when switching from solid to rendered viewto Persistent Data is now shared between F12 renders and viewport rendering (doubles up, leading to out of memory)The data is not shared between final and viewport render, as there may be differences between the settings. In principle we could share some data if the settings are the same, but this is a known limitation and beyond the scope of a bug report.
Persistent data should be expected to use more memory, that is documented and not considered a bug.