Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

[release branch] Continue rendering tile despite errors #10012

Conversation

kkaefer
Copy link
Contributor

@kkaefer kkaefer commented Sep 16, 2017

port of #10011 to the release branch.

Since 9a9408e, we marked tiles as non-renderable if an error occured. This lead to situations where a tile was loaded + parsed successfully, then a revalidation attempt occured (e.g. because the resource was stale) which failed. In this case, we used to mark the tile as non-renderable although we could've used the perfectly parsed (stale) resource.
…perations completed

Previously, when we started a worker operation that eventually throws an exception (e.g. due to the tile not being parseable), and then enqueue another worker operation while the first one is processing, we treated the worker as idle once the first operation's error callback fired, even though the second operation was still in progress. Due to our use of coalescing, I was unable to come up with a reliable test since we'd need to reproduce the behavior described above, which is timing dependent.
Copy link
Contributor

@jfirebaugh jfirebaugh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kkaefer kkaefer merged commit 82bdd52 into release-ios-v3.6.0-android-v5.1.0 Sep 21, 2017
@kkaefer kkaefer deleted the release-ios-v3.6.0-android-v5.1.0__expired-resources branch September 21, 2017 10:21
@friedbunny friedbunny added Core The cross-platform C++ core, aka mbgl rendering labels Sep 25, 2017
@tobrun tobrun mentioned this pull request Sep 26, 2017
19 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Core The cross-platform C++ core, aka mbgl rendering
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants