Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
A resource failed to call destroy
See original GitHub issueOn API 28 after calling startBlur() I noticed in the debug console lots of messages about:
W/System: A resource failed to call destroy.
These messages keep showing even after calling pauseBlur() and they seem to be correlated with the fps setting (the higher the fps, the higher count of messages).
I upgraded from version 1.0.0 to version 1.1.1 thinking it might fix these issues, but there seems to be an additional message now:
V/RenderScript: User-backed allocation failed stride requirement, falling back to separate allocation
and the blur keeps being reapplied, until everything because a consistent color.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Any updates on this?
@boylenssen I was using it in a recyclerview, but after not getting any updates on the issue I went with a simple transparent frame that dims the background.