Fixed
Status Update
Comments
je...@google.com <je...@google.com>
mo...@google.com <mo...@google.com>
ap...@google.com <ap...@google.com> #2
A link to another sample project demonstrating that the leak only happens when using: LocationServices.FusedLocationApi.requestLocationUpdates but does not happen using a deprecated method: googleMap.setOnMyLocationChangeListener.
https://github.com/fernandospr/android-maps-userlocation
fr...@gmail.com <fr...@gmail.com> #3
Hello, I'm also experiencing the memory leak in my activity responsible for the location service.
The implementation of my project is not different from the example project attached by fernando.
The implementation of my project is not different from the example project attached by fernando.
pr...@google.com <pr...@google.com> #4
FYI this memory leak also seems to exist when using the new FusedLocationProviderClient. I took Fernano's sample from comment #2 and hacked it up to use the FusedLocationProviderClient and was still able to observe the leak upon exiting the activity.
Description
Jetpack Compose version: BOM 2024.05.00
Jetpack Compose component(s) used: Image
Android Studio Build: Jellyfish | 2023.3.1 Patch 2 #AI-233.14808.21.2331.11926650, built on June 4, 2024
Kotlin version: 1.9.23
My goal here is to have the colored box on the left match the height of the text, and for the image to be centered in the box.
However, I've discovered that applying a minWidth to the box causes it to gain height as if the image were being scaled to the box's minWidth. I'm not 100% sure, but it looks like the image's
requiredWidth
modifier isn't being accounted for in the intrinsic calculations when the image is a direct child of a Box. Wrapping the image in a Row fixes it, as does removing thedefaultMinSize
modifier on the Box. As you can see in the attached screenshot, it's the Box that has the extra height instead of the image, so that leads me to believe that the Image's intrinsics aren't working how I would expect. If I replace the Image with a Spacer, it also works correctly.I've attached a screenshot of the problem, as well as the image I used in my demo.
Component Summary:
Code: