blender
/
blender
134
398
Fork 581
Code Issues 6.3k Pull Requests 754 Projects 19 Wiki Activity

Viewport Compositing: Scale node does not render correctly, uses a lot of VRAM in 4.1 and crashes in 4.2 #120857

New Issue
Closed
opened 2024-04-20 17:55:41 +02:00 by Fabien · 9 comments
Fabien commented 2024-04-20 17:55:41 +02:00
Copy Link

System Information
Operating system: Windows 11
Graphics card: RTX 3090

Blender Version
Broken: 4.2 alpha (026f8e8bdf - 20/04/2024)
Worked: 4.0

Short description of error
Since 4.1, Viewport compositing Scale using Render Size mode does not give identical results between Viewport and Final Compositing.
The Viewport Compositing of the attached graph also requires a lot more GPU memory, from 3GB to 12GB.
In 4.2, the scene crashes, randomly but 100% reproducible.

Exact steps for others to reproduce the error
The attached scene has a compositing graph that creates a fullscreen animated random value using a noise texture that is scaled to the render size and offset using Scene time.

  • Open the scene and render one frame using F12 to see the final compositing version.
  • Turn on Viewport Compositing.
  • Notice that the Viewport Compositing renders the Scale node with Render Size mode differently from the Final Compositing.
  • In 4.2, simply scrub or select compositing nodes to trigger a crash.

image

**System Information** Operating system: Windows 11 Graphics card: RTX 3090 **Blender Version** Broken: 4.2 alpha (026f8e8bdf68 - 20/04/2024) Worked: 4.0 **Short description of error** Since 4.1, Viewport compositing Scale using Render Size mode does not give identical results between Viewport and Final Compositing. The Viewport Compositing of the attached graph also requires a lot more GPU memory, from 3GB to 12GB. In 4.2, the scene crashes, randomly but 100% reproducible. **Exact steps for others to reproduce the error** The attached scene has a compositing graph that creates a fullscreen animated random value using a noise texture that is scaled to the render size and offset using Scene time. - Open the scene and render one frame using F12 to see the final compositing version. - Turn on Viewport Compositing. - Notice that the Viewport Compositing renders the Scale node with Render Size mode differently from the Final Compositing. - In 4.2, simply scrub or select compositing nodes to trigger a crash. ![image](/attachments/7a28a111-6710-4100-ae7a-7ad720c85151)
randomvalue_viewportcomp.blend
2.7 MiB
image.png
1.3 MiB
Fabien added the
Type
Report
Priority
Normal
Status
Needs Triage
 labels 2024-04-20 17:55:42 +02:00
Iliya Katushenock commented 2024-04-21 13:45:56 +02:00
Member
Copy Link

I can confirm crash in latest 4.2.
But, for some reason, in today lite debug build, with msvc debugging, i getting:
A breakpoint instruction (__debugbreak() statement or a similar call) was executed in blender.exe.

>	ntdll.dll!DbgBreakPoint()	Unknown
 	ntdll.dll!DbgUiRemoteBreakin()	Unknown
 	kernel32.dll!00007ff9dd1c7344()	Unknown
 	ntdll.dll!RtlUserThreadStart()	Unknown
I can confirm crash in latest 4.2. But, for some reason, in today lite debug build, with msvc debugging, i getting: `A breakpoint instruction (__debugbreak() statement or a similar call) was executed in blender.exe.` ``` > ntdll.dll!DbgBreakPoint() Unknown ntdll.dll!DbgUiRemoteBreakin() Unknown kernel32.dll!00007ff9dd1c7344() Unknown ntdll.dll!RtlUserThreadStart() Unknown ```
Iliya Katushenock commented 2024-04-21 13:46:26 +02:00
Member
Copy Link

@OmarEmaraDev /

@OmarEmaraDev /
Omar Emara commented 2024-04-21 14:19:38 +02:00
Member
Copy Link

I can't reproduce the crash myself. Does anyone get a proper stack trace?
@chafouin Do you get any crash file written?

I can't reproduce the crash myself. Does anyone get a proper stack trace? @chafouin Do you get any crash file written?
Fabien commented 2024-04-21 14:28:37 +02:00
Author
Copy Link

The crash txt file is empty for me.

The crash txt file is empty for me.
Blender Bot added
Status
Archived
 and removed
Status
Confirmed
 labels 2024-04-21 14:28:44 +02:00
Fabien reopened this issue 2024-04-21 14:29:34 +02:00
Blender Bot added
Status
Needs Triage
 and removed
Status
Archived
 labels 2024-04-21 14:29:37 +02:00
Fabien commented 2024-04-21 14:40:41 +02:00
Author
Copy Link

Sorry, I misclicked on the "Comment and Close" button.

Address : 0x00007FF68A6E4099
Module  : blender.exe
Thread  : 00001d9c
Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FFD62351421
Module  : VCRUNTIME140.dll
Thread  : 00002904
Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FFD62351421
Module  : VCRUNTIME140.dll
Thread  : 0000047c
Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FFD62351421
Module  : VCRUNTIME140.dll
Thread  : 00003120
Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FFD62351421
Module  : VCRUNTIME140.dll
Thread  : 00005d54
Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FFD62351421
Module  : VCRUNTIME140.dll
Thread  : 000025a4
Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF68A6E4A0A
Module  : blender.exe
Thread  : 00004d70
Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF68A6E4099
Module  : blender.exe
Thread  : 0000065c
Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt
Error loading symbols C:\Users\fabie\Desktop\blender-4.2.0-alpha+main.026f8e8bdf68-windows.amd64-release\blender.pdb
        error:0xc0000005
        size = 95629312
        base=0x00007FF689FD0000

As mentioned above, that crash.txt file is empty.

Sorry, I misclicked on the "Comment and Close" button. ```Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF68A6E4099 Module : blender.exe Thread : 00001d9c Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FFD62351421 Module : VCRUNTIME140.dll Thread : 00002904 Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FFD62351421 Module : VCRUNTIME140.dll Thread : 0000047c Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FFD62351421 Module : VCRUNTIME140.dll Thread : 00003120 Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FFD62351421 Module : VCRUNTIME140.dll Thread : 00005d54 Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FFD62351421 Module : VCRUNTIME140.dll Thread : 000025a4 Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF68A6E4A0A Module : blender.exe Thread : 00004d70 Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF68A6E4099 Module : blender.exe Thread : 0000065c Writing: C:\Users\fabie\AppData\Local\Temp\randomvalue_viewportcomp.crash.txt Error loading symbols C:\Users\fabie\Desktop\blender-4.2.0-alpha+main.026f8e8bdf68-windows.amd64-release\blender.pdb error:0xc0000005 size = 95629312 base=0x00007FF689FD0000 ``` As mentioned above, that crash.txt file is empty.
Iliya Katushenock added
Status
Confirmed
 and removed
Status
Needs Triage
 labels 2024-04-21 14:45:47 +02:00
Omar Emara commented 2024-04-22 11:46:29 +02:00
Member
Copy Link

With regards to the difference between the viewport and final render, this is expected and is a limitation of the viewport compositor, because it clips huge images to sizes that can fit on the GPU. Noting that you are creating images that are 262144 x 262144 in size, which can occupy hundreds of gigabytes of memory.

As for the crash, it is probably related to that huge allocation, and I suspect it is not related to the viewport compositor, but rather, the CPU compositor. Can you try to confirm that by disabling backdrop, closing the image editor and just leaving the 3d view?

With regards to the difference between the viewport and final render, this is expected and is a limitation of the viewport compositor, because it clips huge images to sizes that can fit on the GPU. Noting that you are creating images that are `262144 x 262144` in size, which can occupy hundreds of gigabytes of memory. As for the crash, it is probably related to that huge allocation, and I suspect it is not related to the viewport compositor, but rather, the CPU compositor. Can you try to confirm that by disabling backdrop, closing the image editor and just leaving the 3d view?
Omar Emara commented 2024-04-22 12:17:48 +02:00
Member
Copy Link

@chafouin I submitted a fix for review. But even with the fix, the huge image sizes you are working with will eventually prompt the OS to kill Blender. You need to fix your node tree to avoid the "scale by a factor of 512" bit. It is probably not intentional and not something you want anyways.

@chafouin I submitted a fix for review. But even with the fix, the huge image sizes you are working with will eventually prompt the OS to kill Blender. You need to fix your node tree to avoid the "scale by a factor of 512" bit. It is probably not intentional and not something you want anyways.
Fabien commented 2024-04-22 12:31:14 +02:00
Author
Copy Link

With regards to the difference between the viewport and final render, this is expected and is a limitation of the viewport compositor, because it clips huge images to sizes that can fit on the GPU.

This used to work in 4.0 though, the Scale using Stretch is now stretching the entire image to the render resolution, instead of applying a simple ratio multiplier based on the render resolution.

Noting that you are creating images that are 262144 x 262144 in size, which can occupy hundreds of gigabytes of memory.

Wow okay, I understand why its happening after the scaling, I didn't expect it to actually create such a large image... I know it's a dumb way to create a random value, but I was expecting it to give single pixel to the entire frame.
Having a random value node would be extremely helpful.

As for the crash, it is probably related to that huge allocation, and I suspect it is not related to the viewport compositor, but rather, the CPU compositor. Can you try to confirm that by disabling backdrop, closing the image editor and just leaving the 3d view?

Indeed, it seems to be fine with just the Viewport compositing on. Thanks for looking into it and for the fix.

> With regards to the difference between the viewport and final render, this is expected and is a limitation of the viewport compositor, because it clips huge images to sizes that can fit on the GPU. This used to work in 4.0 though, the Scale using Stretch is now stretching the entire image to the render resolution, instead of applying a simple ratio multiplier based on the render resolution. > Noting that you are creating images that are 262144 x 262144 in size, which can occupy hundreds of gigabytes of memory. Wow okay, I understand why its happening after the scaling, I didn't expect it to actually create such a large image... I know it's a dumb way to create a random value, but I was expecting it to give single pixel to the entire frame. Having a random value node would be extremely helpful. > As for the crash, it is probably related to that huge allocation, and I suspect it is not related to the viewport compositor, but rather, the CPU compositor. Can you try to confirm that by disabling backdrop, closing the image editor and just leaving the 3d view? Indeed, it seems to be fine with just the Viewport compositing on. Thanks for looking into it and for the fix.
Omar Emara commented 2024-04-22 12:49:38 +02:00
Member
Copy Link

This used to work in 4.0 though, the Scale using Stretch is now stretching the entire image to the render resolution, instead of applying a simple ratio multiplier based on the render resolution.

That's true, because in 4.0, we delayed transformations, so scaling never took place at the scale node. This was changed in 4.1 to match the CPU compositor. But GPUs have limitations on how large an image can be, hence the difference and clipping I mentioned. We will probably bring back the 4.0 behavior partially though.

Having a random value node would be extremely helpful.

This is planned. See #112732.

> This used to work in 4.0 though, the Scale using Stretch is now stretching the entire image to the render resolution, instead of applying a simple ratio multiplier based on the render resolution. That's true, because in 4.0, we delayed transformations, so scaling never took place at the scale node. This was changed in 4.1 to match the CPU compositor. But GPUs have limitations on how large an image can be, hence the difference and clipping I mentioned. We will probably bring back the 4.0 behavior partially though. > Having a random value node would be extremely helpful. This is planned. See #112732.
👍 1
Blender Bot added
Status
Resolved
 and removed
Status
Confirmed
 labels 2024-04-23 09:44:49 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
brush-assets-project
blender-v3.3-release
partial-write-refactor
universal-scene-description
fix-121021
blender-v4.1-release
blender-v3.6-release
blender-v3.6-temp_wmoss_animrig_public
temp-sculpt-dyntopo
gpencil-next
anim/animation-id-113594
blender-v4.0-release
blender-projects-basics
bridge-curves
sculpt-blender
asset-browser-frontend-split
asset-shelf
tmp-usd-python-mtl
tmp-usd-3.6
blender-v3.5-release
blender-v2.93-release
realtime-clock
sculpt-dev
bevelv2
xr-dev
v4.1.1
v3.6.11
v3.3.18
v4.1.0
v3.3.17
v3.6.10
v3.6.9
v3.3.16
v3.6.8
v3.6.7
v3.3.14
v4.0.2
v4.0.1
v4.0.0
v3.6.5
v3.3.12
v3.6.4
v3.6.3
v3.3.11
v3.6.2
v3.3.10
v3.6.1
v3.3.9
v3.6.0
v3.3.8
v3.3.7
v2.93.18
v3.5.1
v3.3.6
v2.93.17
v3.5.0
v2.93.16
v3.3.5
v3.3.4
v2.93.15
v2.93.14
v3.3.3
v2.93.13
v2.93.12
v3.4.1
v3.3.2
v3.4.0
v3.3.1
v2.93.11
v3.3.0
v3.2.2
v2.93.10
v3.2.1
v3.2.0
v2.83.20
v2.93.9
v3.1.2
v3.1.1
v3.1.0
v2.83.19
v2.93.8
v3.0.1
v2.93.7
v3.0.0
v2.93.6
v2.93.5
v2.83.18
v2.93.4
v2.93.3
v2.83.17
v2.93.2
v2.93.1
v2.83.16
v2.93.0
v2.83.15
v2.83.14
v2.83.13
v2.92.0
v2.83.12
v2.91.2
v2.83.10
v2.91.0
v2.83.9
v2.83.8
v2.83.7
v2.90.1
v2.83.6.1
v2.83.6
v2.90.0
v2.83.5
v2.83.4
v2.83.3
v2.83.2
v2.83.1
v2.83
v2.82a
v2.82
v2.81a
v2.81
v2.80
v2.80-rc3
v2.80-rc2
v2.80-rc1
v2.79b
v2.79a
v2.79
v2.79-rc2
v2.79-rc1
v2.78c
v2.78b
v2.78a
v2.78
v2.78-rc2
v2.78-rc1
v2.77a
v2.77
v2.77-rc2
v2.77-rc1
v2.76b
v2.76a
v2.76
v2.76-rc3
v2.76-rc2
v2.76-rc1
v2.75a
v2.75
v2.75-rc2
v2.75-rc1
v2.74
v2.74-rc4
v2.74-rc3
v2.74-rc2
v2.74-rc1
v2.73a
v2.73
v2.73-rc1
v2.72b
2.72b
v2.72a
v2.72
v2.72-rc1
v2.71
v2.71-rc2
v2.71-rc1
v2.70a
v2.70
v2.70-rc2
v2.70-rc
v2.69
v2.68a
v2.68
v2.67b
v2.67a
v2.67
v2.66a
v2.66
v2.65a
v2.65
v2.64a
v2.64
v2.63a
v2.63
v2.61
v2.60a
v2.60
v2.59
v2.58a
v2.58
v2.57b
v2.57a
v2.57
v2.56a
v2.56
v2.55
v2.54
v2.53
v2.52
v2.51
v2.50
v2.49b
v2.49a
v2.49
v2.48a
v2.48
v2.47
v2.46
v2.45
v2.44
v2.43
v2.42a
v2.42
v2.41
v2.40
v2.37a
v2.37
v2.36
v2.35a
v2.35
v2.34
v2.33a
v2.33
v2.32
v2.31a
v2.31
v2.30
v2.28c
v2.28a
v2.28
v2.27
v2.26
v2.25
Labels
Clear labels   
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
This issue affects/is about backward or forward 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
Issues relating to Wayland windowing support.

  
Interest
Workbench

  
Interest: X11

Issues relating to Xorg/X11 support.

  
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
Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
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 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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#120857
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?