Closed mHero21 closed 7 months ago
I'm facing this issue too, any update?
Hey everyone,
we noticed and reproduced this issue in our tests but it didn't cause any obstructive effects. Are you noticing any unwanted artifacts due to this warning? I looked into both of these and why are they happening. I found that they are tied to deepar SDK initialization and I don't think they should cause any QoS degradation.
We most definitely have this on our dev roadmap and we will fix this eventually. From the initial triage, this didn't seem like a high priority issue.
Thanks, Darko
This issue leads to crashes in production that are hard to find since the app just hangs and waits forever due to priority inversion. It's very easy to fix. You just need to change the priority of some tasks in your project. Never start a higher priority task within a low priority one.
There were several fixes regarding this or similar issues. I'm closing the issue, but if you are experiencing the issue please leave a comment.
Error Message: Thread running at QOS_CLASS_USER_INTERACTIVE waiting on a lower QoS thread running at QOS_CLASS_DEFAULT. Investigate ways to avoid priority inversions
Reproducer:
Console log: