Optimize image rasterization with willReadFrequently
hints
#12397
+3
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
getImageData
(e.g. for DEM tiles), we reuse the same canvas object and then read it repeatedly for different images. Recent versions of Chrome started throwing this warning in the console:This PR adds
willReadFrequently
hints in two places where it's needed to make sure that getting data out of loaded images is as fast as possible.Launch Checklist
mapbox-gl-js
changelog:<changelog>Improve performance of loading terrain data</changelog>