This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Every tile parser thread needs its own Style object #881
Labels
Comments
Not sure if this was fixed already but being able to load/save the style's state without waiting for the style JSON to load is needed for Android to restore state when a backgrounded application is terminated then restarted in the foreground. |
Nope, we're currently parsing the Style object in the UI thread, unless it's loaded via HTTP. This is a different issue though and captured in #883. |
kkaefer
added a commit
that referenced
this issue
Feb 18, 2015
kkaefer
added a commit
that referenced
this issue
Feb 18, 2015
and remove a few unused variables refs #881
This was referenced Feb 18, 2015
Closed
@kkaefer How critical do you think this is? Is this something that we can push from the iOS beta milestone? What is the practical possibility of multi-threaded mutation right now? |
This is no longer an issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Style objects are currently shared among several threads. They also modify the style object. #879 addresses some of this by locking
StyleBucket
objects. Instead, every tile worker should have its own copy of the Style object so that we can't mutate it while the tile parser is currently using it. In addition to that, Style objects should be fullyconst
; right now we're resolving parse time constants depending on the current tile's zoom level and change the Style object.The text was updated successfully, but these errors were encountered: