Cycles Crash on deleting/hiding all mesh objects with HIP RT (Experimental) #112983

New Issue

Philipp-Kosarev · 2023-09-28T00:12:24+02:00

Philipp-Kosarev commented

2023-09-28 00:12:24 +02:00

System Information
Operating system: Windows 10 Professional (64 bit)
Operating system version: 10.0.19045 Build 19045

Graphics card: AMD Radeon RX 6700 XT
GPU Driver version: 23.20.11.04-230921a-396203C-AMD-Software-Adrenalin-Edition

CPU: AMD Ryzen 7 3800X 8-Core Processor
RAM: 32 GB

Blender Version
Broken: 3.6 and onward (including the 27/09/2023 Blender 3.6.5 daily build version)
Worked: Technically 3.5.1 due to it not having a "HIP RT (Experimental)"
Also surprisingly works on Blender 4.0 Beta.

Short description of error
Cycles with "GPU Compute" and enabled "HIP RT (Experimental)" crashes when scene has no mesh objects or if they are hidden (other objects don't seem to affect it).

Exact steps for others to reproduce the error

In Preferences > System > Cycles Render Devices set AMD Radeon RX 6700 XT as a HIP Render Device
In Preferences > System > Cycles Render Devices enable "HIP RT (Experimental)"
In Render Properties switch Render Engine to Cycles
In Render Properties Choose GPU Compute as a Render Device
Switch Viewport to Rendered
Delete the default cube

Thank you!

**System Information** Operating system: Windows 10 Professional (64 bit) Operating system version: 10.0.19045 Build 19045 Graphics card: AMD Radeon RX 6700 XT GPU Driver version: 23.20.11.04-230921a-396203C-AMD-Software-Adrenalin-Edition CPU: AMD Ryzen 7 3800X 8-Core Processor RAM: 32 GB **Blender Version** Broken: 3.6 and onward (including the 27/09/2023 Blender 3.6.5 daily build version) Worked: Technically 3.5.1 due to it not having a "HIP RT (Experimental)" Also surprisingly works on Blender 4.0 Beta. **Short description of error** Cycles with "GPU Compute" and enabled "HIP RT (Experimental)" crashes when scene has no mesh objects or if they are hidden (other objects don't seem to affect it). **Exact steps for others to reproduce the error** 1. In **Preferences > System > Cycles Render Devices** set AMD Radeon RX 6700 XT as a HIP Render Device 2. In **Preferences > System > Cycles Render Devices** enable "HIP RT (Experimental)" 3. In Render Properties switch Render Engine to Cycles 4. In Render Properties Choose GPU Compute as a Render Device 5. Switch Viewport to Rendered 6. Delete the default cube Thank you!

Philipp-Kosarev added the

labels 2023-09-28 00:12:25 +02:00

YimingWu commented

2023-09-28 04:28:39 +02:00

Hi @Philipp-Kosarev , it would be helpful if you can give us the crash log, see manual for instructions.

Since 4.0 is working, I'd suggest simply go for the newer version. This sounds like a small corner case that might already be fixed, but I'm not sure whether there is any specific commit that's gonna be backported.

Hi @Philipp-Kosarev , it would be helpful if you can give us the crash log, see [manual for instructions](https://docs.blender.org/manual/en/3.6/troubleshooting/crash.html#windows). Since 4.0 is working, I'd suggest simply go for the newer version. This sounds like a small corner case that might already be fixed, but I'm not sure whether there is any specific commit that's gonna be backported.

YimingWu added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-09-28 04:28:50 +02:00

Philipp-Kosarev commented

2023-09-28 19:52:28 +02:00

Hello,

I've set temp directory to Desktop, but it only generates an empty folder.
Am I misunderstanding how the crash report works?

Hello, I've set temp directory to Desktop, but it only generates an empty folder. Am I misunderstanding how the crash report works?

explorer_BpjszV8us0.png

33 KiB

Pratik Borhade commented

2023-10-20 08:55:18 +02:00

Please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to reproduce the
error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them
to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

Please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer).![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

Philipp-Kosarev commented

2023-10-20 13:18:05 +02:00

Thank you.

Starting Blender with blender_debug_gpu.cmd did generate crash logs.
There wasn't a [project name].crash.txt in the Temp folder. Attached is a screenshot showing all .txt files in it.

Thank you. Starting Blender with `blender_debug_gpu.cmd` did generate crash logs. There wasn't a `[project name].crash.txt` in the Temp folder. Attached is a screenshot showing all .txt files in it.

blender_debug_output.txt

39 KiB

explorer_azalXvPoTm.png

69 KiB

blender_system_info.txt

16 KiB

Pratik Borhade commented

2023-10-23 08:11:02 +02:00

Thanks. Not really able spot crash related info in blender_debug_output.txt
Could you check whether situation has improved in recent 4.0/4.1 builds?: https://builder.blender.org/download/daily/

Thanks. Not really able spot crash related info in `blender_debug_output.txt` Could you check whether situation has improved in recent 4.0/4.1 builds?: https://builder.blender.org/download/daily/

Philipp-Kosarev commented

2023-10-23 16:12:59 +02:00

Looks like the bug persists in blender-4.0.0-beta+v40.c7a6ede99690-windows.amd64-release and blender-4.1.0-alpha+main.65a6350250c2-windows.amd64-release. When I opened the issue it seemed to work on 4.0.0, could be the problem of my testing though.
Could it be an issue on AMD's side?

Looks like the bug persists in `blender-4.0.0-beta+v40.c7a6ede99690-windows.amd64-release` and `blender-4.1.0-alpha+main.65a6350250c2-windows.amd64-release`. When I opened the issue it seemed to work on 4.0.0, could be the problem of my testing though. Could it be an issue on AMD's side?

debug_logs blender-4.1.0-alpha+main.65a6350250c2-windows.amd64-release.7z

9.9 KiB

debug_logs blender-4.0.0-beta+v40.c7a6ede99690-windows.amd64-release.7z

10 KiB

kick-skii commented

2023-12-25 19:32:35 +01:00

this issue is still a problem
it only occurs when using HiP-RT
my hardware is
AMD Ryzen 5980HX
AMD Radeon 6800M
I'm using blender 4.0.2 with the latest AMD driver 23.12.1

edit:checked this issue is also on 3.6 builds
as a workaround for now i have to make an object outside the collection groups and it no longer crashes after that

Edit 2: just adding to my workaround to prevent the bug i have a single 0.01mm tirangle when i render with hiprt in my scene at 0,0,0 with selectablity turned off outside of all sub collection in the scene collection the triangle is not assigned a material is only there to prevent the "crash"

this issue is still a problem it only occurs when using HiP-RT my hardware is AMD Ryzen 5980HX AMD Radeon 6800M I'm using blender 4.0.2 with the latest AMD driver 23.12.1 edit:checked this issue is also on 3.6 builds as a workaround for now i have to make an object outside the collection groups and it no longer crashes after that Edit 2: just adding to my workaround to prevent the bug i have a single 0.01mm tirangle when i render with hiprt in my scene at 0,0,0 with selectablity turned off outside of all sub collection in the scene collection the triangle is not assigned a material is only there to prevent the "crash"

kick-skii commented

2023-12-25 19:40:35 +01:00

here are logs as advised above to the other user
these were generated using the RC 4.0.3 build
its also an issue on 4.1.0 build

here are logs as advised above to the other user these were generated using the RC 4.0.3 build its also an issue on 4.1.0 build

blender_system_info.txt

24 KiB

blender_debug_output.txt

145 KiB

Pratik Borhade added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-12-26 04:57:53 +01:00

Pratik Borhade commented

2024-01-16 10:33:03 +01:00

cc @BrianSavery

Pratik Borhade added the

Module

Render & Cycles

label 2024-01-16 10:33:12 +01:00

Germano Cavalcante referenced this issue

2024-01-18 13:55:57 +01:00

Crashes when rendering Cycles #117229

Brian Savery (AMD) commented

2024-01-31 16:25:41 +01:00

CC-ing @salipour who is taking over for AMD.

Pratik Borhade commented

2024-02-20 06:50:28 +01:00

Okay. BTW @Alaska can you confirm? you've HIP-RT compatible GPU IIRC? 🙂

Alaska commented

2024-02-20 08:40:41 +01:00

I can confirm this issue in Blender 3.6.8, 4.0.2 and these versions of Blender 4.1 and 4.2:
4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-02-19 21:26, hash: 42a74a28f212
4.2.0 Alpha, branch: main, commit date: 2024-02-20 00:21, hash: 7ed02da2bef4

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: AMD Radeon RX 7800 XT ATI Technologies Inc. 4.6.0 Core Profile Context 24.1.1.240110

I can confirm this issue in Blender 3.6.8, 4.0.2 and these versions of Blender 4.1 and 4.2: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-02-19 21:26, hash: `42a74a28f212` 4.2.0 Alpha, branch: main, commit date: 2024-02-20 00:21, hash: `7ed02da2bef4` **System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: AMD Radeon RX 7800 XT ATI Technologies Inc. 4.6.0 Core Profile Context 24.1.1.240110

Alaska added

and removed

labels 2024-02-20 08:40:53 +01:00

Pratik Borhade commented

2024-02-20 09:47:01 +01:00

Thanks. We're raising priority of crash reports which are easy to run into.

Pratik Borhade added

and removed

labels 2024-02-20 09:47:15 +01:00

Alaska referenced this issue

2024-02-20 15:41:38 +01:00

Cycles MetalRT: Deleting all objects in scene results in Blender crash #118514

Brecht Van Lommel commented

2024-02-28 19:19:03 +01:00

@salipour, any chance to have this fix for 4.1, planned for 3 weeks from now?

Not sure if it's an issue in HIP-RT or Cycles code. But either way, I guess it's possible to not create and try to intersect a BVH at all if the scene is empty, if somehow the BVH code can't easily work without any objects.

@salipour, any chance to have this fix for 4.1, planned for 3 weeks from now? Not sure if it's an issue in HIP-RT or Cycles code. But either way, I guess it's possible to not create and try to intersect a BVH at all if the scene is empty, if somehow the BVH code can't easily work without any objects.

Sahar A. Kashi commented

2024-02-28 23:56:05 +01:00

The fix for this is in our latest HIP-RT SDK. I can open a pull request with updated API and changes that make Cycles compatible with HIP-RT version 2.2. Here is the change list.
In order for version 2.2 to work, AMD needs to add new shader binaries to the driver and a driver update is necessary for users. The change on the app side is relatively harmless but will break HIP-RT on older drivers.
Alternatively, I can add a check inside the bvh builder to check if a scene is empty and return the call without invoking HIP-RT.

The fix for this is in our latest HIP-RT SDK. I can open a pull request with updated API and changes that make Cycles compatible with HIP-RT version 2.2. Here is the [change list](https://projects.blender.org/salipour/AMD_HIPRT/commit/032887e4a00535a1c0a80eb3b5f354e2857da8c9). In order for version 2.2 to work, AMD needs to add new shader binaries to the driver and a driver update is necessary for users. The change on the app side is relatively harmless but will break HIP-RT on older drivers. Alternatively, I can add a check inside the bvh builder to check if a scene is empty and return the call without invoking HIP-RT.

Brecht Van Lommel commented

2024-02-29 13:22:28 +01:00

I think for Blender 4.1 it's better to add a check in the BVH builder.

For the driver update, does that mean it we would require ROCm 6 in general for HIP and HIP-RT?

I think for Blender 4.1 it's better to add a check in the BVH builder. For the driver update, does that mean it we would require ROCm 6 in general for HIP and HIP-RT?

Sahar A. Kashi commented

2024-02-29 19:36:12 +01:00

The driver will continue to support both ROCm 6 and pre ROCm 6 for a while and Cycles functionality will not break with driver updates.

Sahar A. Kashi referenced this issue

2024-03-01 02:28:23 +01:00

Cycles: Fix for empty scene crash on HIP-RT #118944

Brecht Van Lommel referenced this issue from a commit

2024-03-05 19:54:44 +01:00

Fix #112983: Cycles HIP-RT crash on deleting all objects

Brecht Van Lommel closed this issue

2024-03-05 19:55:28 +01:00

Blender Bot added