search

LuxCoreRender / BlendLuxCore

Blender Integration for LuxCore
GNU General Public License v3.0
735 stars 91 forks source link

System and Blender Crashes with OpenCL - possible TDR Delay trip? #600

Open djtutorials opened 3 years ago

djtutorials commented 3 years ago

.blend file: Default Cube

Steps to reproduce: materials using ramp node or normal maps.

OS: Windows 10 Blender version: 2.83 & 2.9 LuxCore version: 2.4 and 2.5 Beta 1

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/94672701-system-and-blender-crashes-with-opencl-possible-tdr-delay-trip?utm_campaign=plugin&utm_content=tracker%2F80143047&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F80143047&utm_medium=issues&utm_source=github).
Theverat commented 3 years ago

Steps to reproduce: materials using ramp node or normal maps.

Doesn't sound like the default cube to me. Please provide a working testscene.

What does "TDR Delay trip" mean?

It would also be a good idea if you could add some info about your system, e.g. GPU model.

djtutorials commented 3 years ago

Hi there-

System: Windows 10 CPU- AMD Ryzen 3960x Threadripper GPU- 2 X Radeon VII with AMD Radeon Pro Qtr 4 2020 Drivers. RAM- 64 GB Drive- 1TB Auros M.2 NVME

If you view directly through the ramp node or a materials output, it will hard crash the computer. Both the Luxcore materials and Cycles materials seem to have this issue. I have provided both in the scene attached below. This is an issue in both 2.4 and 2.5BETA 1. FYI- this was not an issue in 2.3.

Scene https://drive.google.com/drive/folders/11Xb6bpUc2-e0mDkCcb_cPN3qBRpd2pl3?usp=sharing ramp_node_issue-20201201T211328Z-001.zip

TDR Delay trip means that sometimes, when the GPU is rendering/compiling, it can trip Windows TDR delay functions and hard crash windows. This was especially a problem early this year with AMD non-pro drivers. I bring this up because it looks very similar to what was happening in Cycles/Prorender and was resolved mid-year and in pro-drivers for AMD.

From AMD Website: "Overview. TDR is a Windows® operating system feature which attempts to reset the graphics driver if it has not responded within a period of time and recovers the system to a functional desktop, without the need for a system reboot."

Theverat commented 3 years ago

I can not reproduce the problem on my system (Windows 10, Nvidia RTX 2080 GPU). Can someone with an AMD card test it?

By the way, the device in the provided scene is actually set to CPU for both viewport and final render, so the GPU should be irrelevant unless OpenCL is used for the imagepipeline and the problem happens there.

djtutorials commented 3 years ago

@Theverat I am fairly certain it is an OpenCL/AMD specific issue...

Librebowski commented 3 years ago

Of course you cant reproduce on Nvidia. this is an AMD issue and its unusable as of now.