wangela
commented
9 months ago If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@ro0opf Thank you for opening this issue. 🙏 Please check out these other resources that might help you get to a resolution in the meantime:
- Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
- Open a support case - Get 1:1 support in Cloud Console.
- Discord - chat with other developers
- StackOverflow - use the
google-mapstag
This is an automated message, feel free to ignore.
Thanks for stopping by to let us know something could be better!
PLEASE READ
If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.
Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.
If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.
Check for answers on StackOverflow with the google-maps tag.
Please be sure to include as much information as possible:
Environment details
Steps to reproduce
It seems that there is a memory leak issue when using Google Map Compose in the debug environment. The issue occurs even during the build when only Google Map Compose is added to the Activity/Fragment. While the initial entry appears to be fine, subsequent reentries result in significantly slowed performance to the extent that normal usage becomes challenging. It operates normally in the release environment. Can you please look into this for confirmation?
Code example
Stack trace
Following these steps will guarantee the quickest resolution possible.
Thanks!