New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android][AcrylicBlur] Performance Degradation when ThrowStopExceptionOnDraw set to True #7
Comments
have you tried increasing the |
I tried bumping up the I have attached the following image for you to see. The acrylic material frame doesn't show until I click on the toggle button I then changed the
|
You are using it wrong. |
Yeah, I understand it blurs the contents underneath. I think maybe the example image I gave above wasn't the best. I have replaced the background with a pattern so that you can clearly see when it is blurred. In the example below. I have set the With regards to the MaterialFrame in MaterialFrame, I agree that would be somewhat intensive and was a mistake on my part as I forgot to remove the outer Material Frame. To demonstrate the sluggishness, I have attached the following 2 videos of the exact same code and just changing the Sample 1 ThrowStopExceptionOnDraw_False.zip Sample 2 ThrowStopExceptionOnDraw_True.zip In the app that I'm building I have seen the same thing, the more I use it with Here is the updated code for the Gifs/videos above |
thanks for the updated sample, I will investigate |
I'm very fond of tracking memory leaks (not a joke :) |
Now there is something you don't hear everyday :) Hopefully this bug is a good one for you then :) |
Ok so the android material frame isn't leaking: I tested it thoroughly. The Java finalizer is called and the renderer is disposed as well. It's been opened for more than a month now, but they didn't seem to really care about it... |
Thanks so much for you efforts. I will go post on that thread to hopefully get some traction. Just wanted to also say your projects are really fantastic and I just saw your new one with shadows. Its really AWESOME! Keep up the great work bud! |
I dig further, and the more we go back and forth, the more JNI UNHANDLED EXCEPTION stack trace becomes bigger.
And it's just getting repeated countless times:
You can have a look to the 4 logs corresponding to 4 successive tries. log_1.txt First log is 360 lines, second is 937, third one is 1949, last one is 2644. |
That is very interesting. It's almost as if the stack trace isn't being cleared out. Originally, while I was trying to figure out what was causing this issue, I removed all the acrylic blur material frames on one of the pages in the app, and whenever I navigated to it, the performance was all of sudden fine, which really confused me. But with what you posted here now, it all makes sense. |
@mauro-dasilva we made some good progress with the Xamarin.Android bug. Now let's just hope that the "growing" exception stack will be fixed as well. I'm worried they will only fix the logging in adb but some weird bug will remain. |
@mauro-dasilva some update: xamarin/xamarin-android#4987 seems to find a workaround for the exception stack getting bigger and bigger. Just have to throw new StopException each time instead of throwing the static instance :) |
Next version should be published next week |
Awesome! Thansk bud |
should be fixed by https://github.com/roubachof/Sharpnado.MaterialFrame/releases/tag/v1.1.3 AND vs 2019 studio 16.8. |
Visual Studio 16.8 is released \o/ |
let's close this :o) |
Platform (please complete the following information):
Describe the bug
I have noticed that when you set the
ThrowStopExceptionOnDraw
to True on Android, if you navigate around a few pages that have the MaterialFrames with the following settings:The app starts to get slower and slower as you use it and starts to stutter. If you turn
ThrowStopExceptionOnDraw
to False everything works smoothly.To Reproduce
I have attached a sample project, as well as the GIF below. In the sample, I have a few MaterialFrames with the settings specified above and I'm just navigating to that page and back. You will see that the content gets slower to load and even the back arrow animation in the top left starts to stutter.
Screenshots (if applicable)
App1.zip
The text was updated successfully, but these errors were encountered: