Closed Bug 625249 Opened 14 years ago Closed 1 year ago

valgrind warnings in mozilla::FrameLayerBuilder::RemoveDisplayItemDataForFrame

Categories

(Core :: Web Painting, defect)

x86_64
Linux
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: dbaron, Unassigned)

Details

(Keywords: valgrind)

Attachments

(2 files)

Attached file valgrind warnings
In an attempt to reproduce bug 623351, I did a clean build of http://hg.mozilla.org/mozilla-central/rev/f9537a28ce19 and uncommented the line "#define DEBUG_TRACEMALLOC_PRESARENA 1" in layout/base/nsPresArena.h (which most people running valgrind probably don't do, so they wouldn't see this).

While shutting down Firefox after a complete FBTest run (though I suspect much simpler steps would be sufficient), I got the attached warnings.
Attachment #503359 - Attachment description: patch → valgrind warnings
These are still around, though the function is now called mozilla::FrameLayerBuilder::RemoveDisplayItemDataForFrame .

(If you want to test this *right now*, you'll need attachment 522165 [details] [diff] [review] from bug 645423.)
Keywords: valgrind
Summary: valgrind warnings in mozilla::FrameLayerBuilder::UpdateDisplayItemDataForFrame → valgrind warnings in mozilla::FrameLayerBuilder::RemoveDisplayItemDataForFrame
Actually, the difference is really in the optimization.  In an unoptimized build, running browser-chrome mochitests in toolkit/mozapps/extensions, the first warning is this.
Component: Layout: View Rendering → Layout: Web Painting
Severity: normal → S3

FrameLayerBuilder was removed in bug 1726291

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: