Bug: Circle filling flickers on fast circle radius and center update [35823299]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Aug 9, 2013 11:58AM

On fast Circle (with filling and stroke) updating (~10ms) filling flickers on center and radius change. Stroke is drawn fine.

What steps will reproduce the problem? Please provide a link to a
demonstration page if at all possible, or attach code.
1. Create Circle with some center and radius.
2. Update Circle radius and center (by a little bit) in any repeatable timer with refresh delay ~10ms.
3. Look at circle filling flickering.

*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************

Comments

an...@gmail.com <an...@gmail.com> #2Aug 26, 2013 03:06PM

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

an...@gmail.com <an...@gmail.com> #3Sep 9, 2013 10:27PM

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.

ri...@gmail.com <ri...@gmail.com> #4Nov 7, 2013 05:27PM

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.

fl...@gmail.com <fl...@gmail.com> #5Dec 2, 2013 07:09PM

Leak still present in 2019 on latest play-services-location 16.0.0. 3+ years since first reported via linked Github issue, no fix or hint of acknowledgment. Clown college grade software engineering.

ca...@googlemail.com <ca...@googlemail.com> #6Feb 7, 2014 05:24PM

I am also still experiencing this!

fl...@gmail.com <fl...@gmail.com> #7Feb 7, 2014 05:32PM

Still present in 'com.google.android.gms:play-services-location:17.0.0'

As an alternative I am using FusedLocationProviderClient with PendingIntent:

IntentFilter intentFilter = new IntentFilter(ACTION_LOCATION);
registerReceiver(locationReceiver, intentFilter);
mFusedLocationClient.requestLocationUpdates(mLocationRequest, locationPendingIntent);
and
unregisterReceiver(locationReceiver);
mFusedLocationClient.removeLocationUpdates(locationPendingIntent)

Here is forked LocationUpdates repo with LeakCanary installed and an option to switch between LocationCallback and PendingIntent. LeakCanary not reporting anything when using PendingIntent.

https://github.com/dejandobnikar/location-samples/tree/master/LocationUpdates

ca...@googlemail.com <ca...@googlemail.com> #8Feb 7, 2014 05:46PM

Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here

https://goo.gl/TbMiIO and reference this bug for context.

fl...@gmail.com <fl...@gmail.com> #9Apr 7, 2014 06:12PM

Comment #8

, the one thing that would matter to address is how to *actually* get this issue fixed. It appears pointless to file a new issue, and unclear where to do so, as this issue has not received attention from Google's side throughout the years despite quite a few people starring it and bug reports in different places. The continued existence of the bug was confirmed not long ago in prior comments by different people. I've just confirmed it again myself on R Beta 3.

du...@gmail.com <du...@gmail.com> #10May 21, 2014 02:06PM

According to some Google DevRel it might soon be fixed, see the answer (from 8 days ago) here:

https://github.com/googlecodelabs/while-in-use-location/issues/7

ki...@gmail.com <ki...@gmail.com> #11Apr 8, 2015 11:45PM

This issue still exists, how can this be prioritized?

au...@gmail.com <au...@gmail.com> #12Apr 17, 2015 03:42PM

There is an issuetracker Component available these days for Play Services Location: https://issuetracker.google.com/components/1065160

Maybe move this issue to that Component to track it better?

bh...@gmail.com <bh...@gmail.com> #13May 11, 2015 08:38PM

I can't move it right now, but I think it's ok to stay here.

As I wrote in the code lab issue, I misunderstood when the rewrite went out (which should fix the issue).

It goes live in version 20 (current version location 19.0.1). The engineer who wrote the rewrite checked and wasn't seeing the same issue, i.e., it should be resolved.

However, that does mean we have to wait until 20 is released. I can check in again here when it's live for you to double check.

gi...@gmail.com <gi...@gmail.com> #14May 12, 2015 12:20AM

8 ram

lo...@gmail.com <lo...@gmail.com> #15Jan 4, 2016 09:56AM

I haven't been on location in awhile, but I wanted to follow up on this.

The issue should be resolved with the play-services-location:20.0.0 release from my understanding.

ar...@gmail.com <ar...@gmail.com> #16Jan 28, 2016 09:47AM

[Comment deleted]

ki...@gmail.com <ki...@gmail.com> #17Mar 8, 2016 09:18AM

@Gigs Could you post some code regarding your canvas workaround?

ko...@gmail.com <ko...@gmail.com> #18Apr 6, 2016 11:24AM

The problem still occur. Is it possible to fix it soon?

ty...@gmail.com <ty...@gmail.com> #19May 12, 2016 05:03PM

Guys, the problem still occurs. Almost 3 years since first report. It's not funny.

kj...@gmail.com <kj...@gmail.com> #20Jul 7, 2016 02:59PM

This is ridiculous.

de...@gmail.com <de...@gmail.com> #21Aug 2, 2016 09:32AM

When problem will be solved?

lm...@google.com <lm...@google.com> Aug 2, 2016 11:46PM

Accepted by lm...@google.com.

ty...@gmail.com <ty...@gmail.com> #22Sep 22, 2016 10:08AM

Good news. But how soon we can expected new patched version?

lm...@google.com <lm...@google.com> #23Oct 25, 2016 01:15AM

Marked as fixed.

Thanks for the reports of this issue. This was a threading issue buried deep within our rendering code, but this issue is now fixed with the Google Play Services 9.8 release!

See the Android Maps API release notes here:

https://developers.google.com/maps/documentation/android-api/releases#october_24_2016

lo...@gmail.com <lo...@gmail.com> #24Oct 25, 2016 07:18AM

[Comment deleted]

lo...@gmail.com <lo...@gmail.com> #25Oct 25, 2016 07:19AM

Great, thanks!

ki...@gmail.com <ki...@gmail.com> #26Oct 26, 2016 10:38AM

3 years in the making! Thanks for fixing!

jr...@gmail.com <jr...@gmail.com> #27Oct 26, 2016 10:45AM

I'll add my thanks. Maybe you can let one of us try to fix it if it's been more than 12 months? I'm sure quite many of us would be willing to help out.

[Deleted User] <[Deleted User]> #28Mar 24, 2017 01:42PM

I am dealing with the same issue drawing a polygon. I am only updating at 30 times a second and it flickers like crazy. My current test is just a triangle. I am going to have fudge this implementation and use a marker as they seem to be the only thing that can be updated frequently. Then I need to figure out how to scale the marker icon to meet exact map distances. It would be nice if there was a map animation layer or something that allowed one to update elements and have the rendering sync up with the map.

al...@gmail.com <al...@gmail.com> #29May 10, 2017 02:36PM

Same problem when adjusting the size for a Polygon. Any updates on a possible fix ?

kh...@gmail.com <kh...@gmail.com> #30Dec 20, 2017 10:05AM

i set the circle around the maker which have more than specific time, it works find but the animation of the circle radius keep increasing continuously.

does anyone have any idea why this happen & how can I solve it ?

sm...@gmail.com <sm...@gmail.com> #31Jan 2, 2018 02:54PM

Having the same flickering issue when calling 'setPoints' on a polygon. Any updates?

o....@googlemail.com <o....@googlemail.com> #32Apr 18, 2019 08:19AM

I can confirm this happens when calling 'setPoints' on a polygon! Please have a look at that!

ka...@gmail.com <ka...@gmail.com> #33Sep 19, 2022 12:47PM

Still having this issue

re...@gmail.com <re...@gmail.com> #34Apr 26, 2023 04:24PM

I'm having the same problem with Polygon in Jetpack Compose.