While using your SDK, I've observed that even when there are no ad plays or calls, a thread named "ConfigBootstrapHandle" continues to occupy a considerable portion of memory. When advertising is invoked, the combined memory usage of the "TIM-ma" thread and the aforementioned thread becomes quite substantial. Given that our project is a game and we prioritize memory sensitivity, we've also noticed noticeable memory fluctuations. While these may not necessarily be caused by your SDK, we kindly request your assistance in investigating and optimizing this situation. We will also reach out to developers from other advertising platforms for further examination. Could you please take a look and provide optimization suggestions, or guide us on how to avoid this issue? Your support is much appreciated.
Thank you.
Here are some screenshots of my memory monitoring.
Hello, developers at InMobi,
While using your SDK, I've observed that even when there are no ad plays or calls, a thread named "ConfigBootstrapHandle" continues to occupy a considerable portion of memory. When advertising is invoked, the combined memory usage of the "TIM-ma" thread and the aforementioned thread becomes quite substantial. Given that our project is a game and we prioritize memory sensitivity, we've also noticed noticeable memory fluctuations. While these may not necessarily be caused by your SDK, we kindly request your assistance in investigating and optimizing this situation. We will also reach out to developers from other advertising platforms for further examination. Could you please take a look and provide optimization suggestions, or guide us on how to avoid this issue? Your support is much appreciated.
Thank you.
Here are some screenshots of my memory monitoring.