-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CustomGeometrySource's java peer assertions fail when source is removed #12551
Comments
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
@LukasPaczos Can you tell me if this issue is being worked on? I'm a Mapbox enterprise customer, and this bug is currently blocking shipping my application. |
This is probably not the right fix, but this commit does seem to fix the crashes: trailbehind@a6c8814 |
Thanks for the heads up @JesseCrocker. We'll look into this in next sprint, beginning next week. |
Hey @JesseCrocker, thanks for a suggestion. We've considered that before but didn't pull the trigger because we had a general refactor in mind. Since that didn't happen and is not on a backlog, for now, we might implement this workaround. |
I'm not sure this is completely fixed. We have a custom geometry source with tiles that take 1-2 seconds to load. We also provide the ability to change the basemap style. If you change them quickly, or occasionally randomly, we are getting a crash with this error:
Through debugging, we're definitely getting this error after we've changed styles but when there are still tiles being generated. Should I create a new issue for this? |
I am facing the same problem as @bentomas. I already tried the last version
|
Refs #12517 (review).
The java peer assertions for
CustomGeometrySource::fetchTile
andCustomGeometrySource::cancelTile
can fail when we remove the source on the main thread but the requests are still being processed on worker threads.Temporary workaround - a small delay between removing the layer and removing the source is enough for the worker threads to finish and then we can safely remove the source.
/cc @asheemmamoowala
The text was updated successfully, but these errors were encountered: