Dima Saviuk

@hugomc92 It indeed seems to be the case, but I'm afraid there's nothing reasonable I can do to fix it. I'm not sure what they changed internally so it stopped...

There's a RenderEffectBlur to replace RenderscriptBlur on newer APIs. Hope that works for you. It's way simpler than the Vulkan or OpenGL approach, so I'm not really considering them

Ah, by "under" you meant before Android 31. No, I'm not planning anything. I don't think it's worth the effort

The Toolkit could be integrated more or less painlessly, but there are still a couple of problems with it. 1) It [allocates](https://github.com/android/renderscript-intrinsics-replacement-toolkit/blob/main/renderscript-toolkit/src/main/java/com/google/android/renderscript/Toolkit.kt#L236) a bitmap on each blur call, which is...

Provide the details required in the bug report. There's not much I can do without steps to reproduce

I don't think it's BlurView's problem. Something is holding that lock libart waits on (`WaitHoldingLocks`). Most likely it's just an unlucky coincidence that the BlurView happens to execute the blur...

If you want me to help, please put more effort into describing the issue. Post your screenshots, layout, and how you set up your BlurView. Or just send a sample...

> the blur does not blur the img What image? > but it blurs what is on the fragment under the bottomsheet That's basically what it's supposed to do -...

If you're using Glide or some other image loading library, the cause might be [this](https://github.com/Dimezis/BlurView/issues/150)

@wang0826jj You can wrap the `RenderscriptBlur`, try-catch the `blur` method and recreate the blur Algorithm on exception. But really Glide should just fix this, calling `releaseAllContexts` in a library is...