Reproduction steps:
1. Open the attached “repro_IN-99268“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Set your graphics API to “Direct3D12” (“Edit - > Project Settings… → Player → Graphics APIs for Windows“
4. Either interact with the Scene view or enter the Play Mode
5. Observe the Console

Expected result: “Attempting to draw with missing bindings“ warning is thrown once, and there’s an indication in the warning of what caused it
Actual result: “Attempting to draw with missing bindings“ warning is thrown each frame, and there’s no indication in the warning of what caused it

Reproducible with: 6000.0.20f1, 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Not reproducible with: 2022.3.62f1, 6000.0.19f1

Reproducible on: Windows 10 (22H2), Windows 11 (24H2)
Not reproducible on: macOS Sequoia 15.3 (M2 Ultra)

Notes:

• Reproducible in Player
• Reproducible with: DirectX12
• Partly reproducible with: Vulkan - warning is reproducible, but is only thrown once
• Not reproducible with: DirectX11, OpenGL ES 3.2, Metal
• Metal throws “Metal: Vertex or Fragment Shader "Shader Graphs/TestShaderGraph" requires a ComputeBuffer at index 8 to be bound, but none provided. Skipping draw calls to avoid crashing.“ warning, and only once - a good example of expected result with DirectX12
• Reporter experiences a crash (without stack trace) after the error is spammed for a prolonged amount of time (~30 minutes to 1 hour) on their specific project (which is not the repro project for this case)