Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.44f1
2022.3.48f1
6000.0.20f1
Issue ID
UUM-82696
Regression
No
[Android] Semaphore.WaitForSignal causes ~200ms stalls when Dithering Node in a ShaderGraph is enabled on Samsung J7
Steps to reproduce:
1. Open the attached user's project "URPRepro.zip"
2. Open "Assets/Materials/Background.shadergraph"
3. Make sure that the Dither Node is connected to the output
4. Make sure Development build and Auto Connect Profiler is enabled
5. Build to a Samsung Galaxy J7
6. Observe the Profiler or using 3 fingers tap on the screen to open the display stats UI and observe the reported average FPS
Expected results: Enabling a Dither Node in a ShaderGraph does not cause Semaphore.WaitForSignal to take up 200ms
Actual results: Semaphore.WaitForSignal causes ~200ms stalls when Dither Node in a ShaderGraph is enabled on Samsung J7
Reproducible with: 2021.3.44f1, 2022.3.48f1, 6000.0.20f1
Reproducible with these devices:
VLNQA00288 - Samsung Galaxy J7 (SM-J730F), CPU: Exynos 7 Octa 7870, GPU: Mali-T830, OS: 8.1.0
Samsung Galaxy A5 (user)
Samsung Galaxy A32 (user)
Samsung Galaxy S10e (user)
Not reproducible with these devices:
VLNQA00111 - Samsung Galaxy J5 (2016) (SM-J510FN), CPU: Snapdragon 410 MSM8916, GPU: Adreno 306, OS: 7.1.1
VLNQA00482 - samsung Galaxy A32 5G (SM-A326B), CPU: MediaTek Dimensity 720 (MT6853), GPU: Mali-G57 MC3, OS: 12
VLNQA00282, Samsung Galaxy S10e (SM-G970U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00598 - samsung Galaxy Fold (SM-F900F), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00547 - samsung Galaxy Tab A8 (SM-X200), CPU: Unisoc Tiger T618, GPU: Mali-G52, OS: 13
VLNQA00422 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 11
VLNQA00423 - Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 9
VLNQA00202 - Samsung Galaxy Note 9 USA (SM-N9600), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 9
Notes:
-According to the user "Application.targetFrameRate is set to 300 on a 60 hz device, but the issue happens if we don't set targetFrameRate"
-Issue reproduces with Vulkan and OpenGLES 3
-The slowdown (Semaphore.WaitForSignal) is caused by the Dithering Node used in the "Assets/Materials/Background.shadergraph" Shader Graph
-Profiler data of the affected devices is attached ("SamsungJ7_6000_0_20f1.data")
-Profiler data of the affected user device is attached ("Galaxy A32.data")
-
kevinrankin374
Sep 23, 2024 17:40
Recovering From Fake Online Investment Schemes
I had been a loyal customer of a particular investment company for several months investing my funds, using their services without issue. The company suddenly closed my account and l was unable to withdraw. Desperate for a resolution I discovered Lost Recovery Masters, a special legal recovery expert intelligence group service specializing in resolving issues with unscrupulous and fake online investment companies. Lost Recovery Masters successfully recouped all my lost funds to my immense relief. I am grateful for Lost Recovery Masters, As a form of appreciation this was the best I could do for them. I highly recommend their services. If you need their assistance, contact them on
Website: (lostrecoverymasters . com)
Whatsapp +44(7-5-3-7-1-0-5-9-2-1
Support Email (Support @ lostrecoverymasters . com)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
- SamplerState Property Missing Anisotropic Filtering
- Visual glitches when using Handles API
- The RGBA color values are inconsistent when comparing two identical colors set in the Inspector
Resolution Note:
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.