Realtime compositor crash with GPU OIDN when moving object #120240

New Issue

and removed

2024-04-04 08:54:52 +02:00

labels 2024-04-04 08:44:34 +02:00

Tao-Mao commented

Hi Pratik, thanks for the feedback. I might accidentally turned the real time compositor off. I just tried the same file again and yes, it crashes with the realtime compositor on. When I turned it off, it was working fine. You can try to turn it on and move the objects around. You have to try a few times, it doesn't happen straight away when you move objects. Here is a new log file. Don't know if you can find anything new.

Scene 03_V6.crash.txt

47 KiB

Pratik Borhade commented

2024-04-04 09:34:15 +02:00

Thanks. Looking at the logs, crash is probably introduced with f4f22b64eb
BTW Still not really able to reproduce the crash. What preference is selected for GPU acceleration (CUDA/OptiX)?
I tried moving object few times with G hotkey and also with tweak tool but render updates fine without crash.

Thanks. Looking at the logs, crash is probably introduced with f4f22b64ebfc99579d8b14bace9b2edaae6ec9a4 BTW Still not really able to reproduce the crash. What preference is selected for GPU acceleration (CUDA/OptiX)? I tried moving object few times with G hotkey and also with tweak tool but render updates fine without crash.

Tao-Mao commented

2024-04-04 11:03:55 +02:00

Hi Pratik, it happens both on CUDA and Optix. I've recorded the interface.

Recording 2024-04-04 220249.mp4

34 MiB

Recording 2024-04-04 220111.mp4

9.7 MiB

Tao-Mao commented

2024-04-04 11:12:47 +02:00

Hi pratik, I just found the crashing happened when I created an individual window for render preview. If I use my current 3d viewport to preview it's fine. You can try to create a new window to see if the crashing happens on your end. Thanks

Pratik Borhade commented

2024-04-08 10:37:24 +02:00

Thanks, still not able reproduce :/
@OmarEmaraDev , can you check?

Thanks, still not able reproduce :/ @OmarEmaraDev , can you check?

Omar Emara commented

2024-04-08 10:54:08 +02:00

I can't reproduce either. But I don't have GPU Denoising support or OptiX/CUDA, so I wouldn't expect to reproduce it.

@PratikPB2123 However, f4f22b64eb is not part of 4.1, so it can't be the reason. The code path in the stack trace dates back to v3.6. This is is a 4.1 regression, it is probably due to the GPU Denoising feature.

I can't reproduce either. But I don't have GPU Denoising support or OptiX/CUDA, so I wouldn't expect to reproduce it. @PratikPB2123 However, f4f22b64eb is not part of 4.1, so it can't be the reason. The code path in the stack trace dates back to v3.6. This is is a 4.1 regression, it is probably due to the GPU Denoising feature.

Pratik Borhade commented

2024-04-08 10:57:36 +02:00

Oh, okay. Thanks. 4.1 branch is labelled in commit though: image

Oh, okay. Thanks. 4.1 branch is labelled in commit though: [image](/attachments/bd7f50b3-cb92-4b31-ad86-81f5624a1602)

image.png

44 KiB

Omar Emara commented

2024-04-08 10:59:45 +02:00

@PratikPB2123 I saw that. But Gitea seems wrong here. You can manually check the glare node in 4.1 and see if it has the Bloom option added in that commit.

Pratik Borhade commented

2024-04-08 11:01:56 +02:00

Yes, did that already. I trusted the gitea tag though 😅
Anyways, resetting the status :)

Yes, did that already. I trusted the gitea tag though 😅 Anyways, resetting the status :)

Pratik Borhade added

and removed

2024-04-11 11:11:32 +02:00

labels 2024-04-08 11:02:06 +02:00

Pratik Borhade changed title from ~~Blender 4.1 quits constantly~~ to Realtime compositor crash with GPU OIDN when moving object

2024-04-08 11:03:32 +02:00

Raimund Klink commented

Couldn't reproduce the crash.
Win 11, Blender 4.1, RTX 2000 Ada

Couldn't reproduce the crash. Win 11, Blender 4.1, RTX 2000 Ada

👍 1

Alaska commented

2024-04-11 15:17:08 +02:00

I can't reproduce with the system below. Could there be a issue with your GPU drivers? Could you try re-installing your GPU drivers from here? https://www.nvidia.com/download/index.aspx

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86
Blender version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270

I can't reproduce with the system below. Could there be a issue with your GPU drivers? Could you try re-installing your GPU drivers from here? https://www.nvidia.com/download/index.aspx **System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86 Blender version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: `40a5e739e270`

Pratik Borhade added

and removed

2024-04-20 13:05:50 +02:00

labels 2024-04-12 08:22:55 +02:00

Tao-Mao commented

Hi Alaska, sorry to bother you again. I tried different ways and the quiting issue remains. This time I work with another scene and it quits even with denoise off. I've attached a new log file and could you have a look to see if you can find something new?

joy 2.blend

73 MiB

joy 2.crash.txt

50 KiB

Tao-Mao commented

2024-04-20 13:11:38 +02:00

Ok, now I'm pretty sure what causes this. I'm using two screens with different resolutions. It's probably the reason cause Blender quiting. When I create a new window and drage this window to another screen, the quiting happens when I click my objects and move around. But when I close this window and split the main interface to create a preview area on one screen, it's totally fine.

Tao-Mao commented

2024-04-20 13:44:16 +02:00

And a quick update, I set my two screens with the same display resolution, the problem is gone. It seems like somehow the different resolution causes Blender's quiting.

Alaska commented

2024-04-20 14:06:14 +02:00

@Tao-Mao Based on the information you've learned, can you please provide full, clear, updated instructions to reproduce the issue?

Tao-Mao commented

2024-04-21 21:56:34 +02:00

Ok I will try my best to describe this, let me know if you'd like to add something more. So I have two monitors, one is 2k and another is 4k. I set the resolution for the two screens as their original settings, which are 25601650 and 38402160 and I connect them to my computer with windows 11(specs showed as my first post). I use the 2k screen as my main display.

When I use Blender, I always create a new window and drag it to my 4k screen to give more space for my Blender's working space. However when I preview the render on the 4k screen and move around objects on another screen, it causes Blender's quiting without any alert information.

So if I split my working space to preview the render on one screen, the issue is gone. Also I tried to set my 4k screen with 2k resolution, which is the same as my main display, the issue seems gone as well even I ise a separated window to preview the render on another screen. Not 100% sure it's the reason but it works for me.

Cheers

Ok I will try my best to describe this, let me know if you'd like to add something more. So I have two monitors, one is 2k and another is 4k. I set the resolution for the two screens as their original settings, which are 2560*1650 and 3840*2160 and I connect them to my computer with windows 11(specs showed as my first post). I use the 2k screen as my main display. When I use Blender, I always create a new window and drag it to my 4k screen to give more space for my Blender's working space. However when I preview the render on the 4k screen and move around objects on another screen, it causes Blender's quiting without any alert information. So if I split my working space to preview the render on one screen, the issue is gone. Also I tried to set my 4k screen with 2k resolution, which is the same as my main display, the issue seems gone as well even I ise a separated window to preview the render on another screen. Not 100% sure it's the reason but it works for me. Cheers

Tao-Mao commented

2024-04-21 21:59:26 +02:00

From my understanding the 4k and 2k display difference might causes some problems, but I don't know if there's a way to surveillant this

Alaska commented

2024-04-22 03:54:06 +02:00

Thanks for the description I ran the test on my computer following these steps. Please correct me if I've done anything wrong:

Connect two monitors to my computer.
Set the main monitor to 3840x2160, set the secondary monitor to 2560x1440.
Open your test file Scene 03_v6.blend in Blender 4.1.0
This file contains two windows. A main window (3D viewport, Properties Editor, Outliner), while the other "secondary window" has just the 3D viewport.
I place the secondary window on my main monitor (4k monitor). And I place the main window on my secondary screen.
Set the secondary window to Cycles rendered view, and enable viewport compositor (It was a step mentioned previously)
Move some objects around in the main window to try and get Blender to crash.

In case things got confusing due to the different "mains and secondaries", here's a video.
The main monitor (3840x2160) is in the middle. While my secondary moniotr (2560x1440) is in the bottom left.

Thanks for the description I ran the test on my computer following these steps. Please correct me if I've done anything wrong: 1. Connect two monitors to my computer. 2. Set the main monitor to 3840x2160, set the secondary monitor to 2560x1440. 3. Open your test file `Scene 03_v6.blend` in Blender 4.1.0 4. This file contains two windows. A main window (3D viewport, Properties Editor, Outliner), while the other "secondary window" has just the 3D viewport. 5. I place the secondary window on my main monitor (4k monitor). And I place the main window on my secondary screen. 6. Set the secondary window to Cycles rendered view, and enable viewport compositor (It was a step mentioned previously) 7. Move some objects around in the main window to try and get Blender to crash. In case things got confusing due to the different "mains and secondaries", here's a video. The main monitor (3840x2160) is in the middle. While my secondary moniotr (2560x1440) is in the bottom left. <video src="/attachments/d152d24c-1a4c-4388-b7b2-5100d7b30ba4" title="Multi-monitor try and get it to crash.mp4" controls></video>

Multi-monitor try and get it to crash.mp4

13 MiB

Tao-Mao commented

2024-04-22 04:04:36 +02:00

I just checked your video, yes it's my case, if you can't replicate this it's probably related to my graphic card

Alaska commented

2024-04-22 04:21:34 +02:00

I also tried it the other way around and couldn't reproduce a crash.

Tao-Mao commented

2024-04-22 04:40:48 +02:00

Yes you are right, I actually change the display to 125% or something, I forgot, will let you know when I'm home, thanks!

Tao-Mao commented

2024-04-22 09:51:35 +02:00

The 2k screen, 2560 one, I used 125% scale, the 4K one, I used 175% scale.

Alaska commented

2024-04-22 13:01:09 +02:00

I re-ran the test with different scaling on each monitor, and I still couldn't reproduce the issue.

I'm setting the issue back to "Needs triage" as I'm not sure what else to ask to gain information that may assist in tracking down the cause.

I re-ran the test with different scaling on each monitor, and I still couldn't reproduce the issue. I'm setting the issue back to "Needs triage" as I'm not sure what else to ask to gain information that may assist in tracking down the cause. <video src="/attachments/2051763c-de0f-4a3f-9e1a-6181a68a4ddf" title="Updated demonstration.mp4" controls></video>

Updated demonstration.mp4

19 MiB

Alaska added

and removed