summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMoonchild <moonchild@palemoon.org>2022-04-18 14:31:55 +0200
committerMoonchild <moonchild@palemoon.org>2022-04-18 14:31:55 +0200
commitc2b4aa8cf2374d6178be94199e6e9def21bad51a (patch)
tree2fee2a7e51d9ef91871e37673c7561fa70d7d165
parent129bb5568d3664cec5d6787eb55225f1561d73ad (diff)
downloaduxp-c2b4aa8cf2374d6178be94199e6e9def21bad51a.tar.gz
Issue #1860 - Follow-up: Make sure we don't add duplicate frames
Changing to vector makes manipulating display list items more risky. This is to make sure we don't inadvertently end up with duplicates in the list of display items avoiding double-free scenarios.
-rw-r--r--layout/base/FrameLayerBuilder.cpp7
1 files changed, 6 insertions, 1 deletions
diff --git a/layout/base/FrameLayerBuilder.cpp b/layout/base/FrameLayerBuilder.cpp
index aa49c74cee..ff4661e1c8 100644
--- a/layout/base/FrameLayerBuilder.cpp
+++ b/layout/base/FrameLayerBuilder.cpp
@@ -162,7 +162,12 @@ void
FrameLayerBuilder::DisplayItemData::AddFrame(nsIFrame* aFrame)
{
MOZ_RELEASE_ASSERT(mLayer);
- mFrameList.AppendElement(aFrame);
+
+ // Make sure we don't add duplicate frames as we're storing these as vectors.
+ // See UXP Issue #1860
+ if (!mFrameList.Contains(aFrame)) {
+ mFrameList.AppendElement(aFrame);
+ }
nsTArray<DisplayItemData*>* array =
aFrame->GetProperty(FrameLayerBuilder::LayerManagerDataProperty());