Adreno 530 glitches and crashes when sorting is on

Unity: Visual Effects

Won't Fix

6.6.X

Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available. Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Steps to Reproduce
1. Open the attached package: Sorting ON.unitypackage
2. Add the Initialize scene to Build Settings
3. Build an .apk
4. Install and run the .apk*on the device

Actual Result

The scene renders glitchy.
After some time, the application crashes.

Expected Result

The scene runs normally without visual glitches or crashes.

Tested on:

Reproducible with: 6000.6.0a1
Not reproducible with: N/A
Can’t test with: N/A

Tested On

*Device/GPU:* Google Pixel (Adreno 530)

Notes

This may also reproduce on Quest 1 and other Adreno 540 devices.
The issue does not occur when Sorting is set to Off
Sorting = Auto: scene becomes glitchy
Sorting = On: scene becomes glitchy and eventually crashes
Sorting = OFF indirect draw ON runs fine (attached video)
Callstack is provided in the comments.

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Issues you vote on will appear here

Adreno 530 glitches and crashes when sorting is on

Unity: Visual Effects

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Adreno 530 glitches and crashes when sorting is on

Unity: Visual Effects

Statuses

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?