Page MenuHomePhabricator

Bug 1602458 - Avoid reallocating opacity bindings and tiles hash maps in TileCacheInstance. r=gw
ClosedPublic

Authored by nical on Dec 9 2019, 5:08 PM.

Diff Detail

Repository
rMOZILLACENTRAL mozilla-central
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

nical created this revision.Dec 9 2019, 5:08 PM
Herald added a project: Restricted Project. · View Herald TranscriptDec 9 2019, 5:08 PM
phab-bot requested review of this revision.Dec 9 2019, 5:08 PM
phab-bot changed the visibility from "Custom Policy" to "Public (No Login Required)".
phab-bot changed the edit policy from "Custom Policy" to "Restricted Project (Project)".
phab-bot removed a project: Restricted Project.
gw accepted this revision.Dec 10 2019, 1:58 AM

Although unlikely, this seems like it could _potentially_ leak memory - if swapping between scenes where the hash keys are regularly different (e.g. the tile x/y offsets)? Probably not an issue in practice, I think, but maybe we should still clear / trim the recycled hash map?

This revision is now accepted and ready to land.Dec 10 2019, 1:58 AM
nical updated this revision to Diff 205479.Dec 10 2019, 4:18 PM

Revision updated.

nical updated this revision to Diff 206624.Dec 12 2019, 9:08 AM

Revision updated.