-
Notifications
You must be signed in to change notification settings - Fork 76
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
After started loadAd in a MAAdView, there are consequences of main thread occupation which caused UI laggy. #282
Comments
Hi @lovecactus we're currently investigating this and will share updates as they become available. |
In our application we are dealing with the same issue. |
Hi @NanaAmoah Any update? 😄 |
@lovecactus @lidorf-gurushots Apologies for the delay here, we're still investigating the issue and will share updates when we have more details |
I'm experiencing the same issue. I hope this gets fixed soon as I can't release to production with a laggy UI. IMHO, this is a critical bug which would undoubtedly lead to 1-star app reviews and upset my customers. Please make this issue a priority. |
@NanaAmoah it is not an "enchancement". It is a bug which causes simulator lags. Even my macbook pro with m2 and 8Gb RAM (which should be enough powerful) has serious lags when I show just a small banner 375x50. I also found out that calling |
@NanaAmoah |
This issue is stale because it has been open for 30 days with no activity. |
Feature Description
We're using the latest AppLovin SDK, with a long list of mediations. However, we noted that after we started to load ads using MAAdView, there was a significant load of the main thread (which eventually caused UI laggy because of the main thread occupation.).
As you can see in the screenshot of instrument logging:
A very high percentage of main thread resources were being used for ALMediationAdapterWrapper. It's not one time but several times in consequences, within seconds, which leads to consequences of slightly, however, noticeable UI freezes.
Is there anything we could do to avoid this?
The text was updated successfully, but these errors were encountered: