Issue 2810253003: [wrapper-tracing] Fix node list leak

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 2810253003: [wrapper-tracing] Fix node list leak (Closed)

Created:
3 years, 8 months ago by Michael Lippautz

Modified:
3 years, 8 months ago

Reviewers:

CC:
chromium-reviews

Target Ref:
refs/branch-heads/3029

Project:
chromium

Visibility:
Public.

[wrapper-tracing] Fix node list leak Only trace node lists that hang of live nodes. BUG=chromium:707544 Review-Url: https://codereview.chromium.org/2809183003 Cr-Commit-Position: refs/heads/master@{#463986} (cherry picked from commit 76798dbd04a30a8e1acdf71ecab93d09dac4ec5b) Review-Url: https://codereview.chromium.org/2810253003 . Cr-Commit-Position: refs/branch-heads/3029@{#690} Cr-Branched-From: 939b32ee5ba05c396eef3fd992822fcca9a2e262-refs/heads/master@{#454471} Committed: https://chromium.googlesource.com/chromium/src/+/fb5051f1e67383a98cf36b21f7cf78a9a44e6301

Created: 3 years, 8 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+20 lines, -11 lines)			Patch
M	third_party/WebKit/Source/core/dom/Document.cpp	View	1 chunk	+3 lines, -11 lines	0 comments	Download
M	third_party/WebKit/Source/core/dom/NodeListsNodeData.h	View	3 chunks	+3 lines, -0 lines	0 comments	Download
M	third_party/WebKit/Source/core/dom/NodeListsNodeData.cpp	View	2 chunks	+14 lines, -0 lines	0 comments	Download

Total messages: 2 (1 generated)

Michael Lippautz

3 years, 8 months ago (2017-04-13 11:34:59 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
fb5051f1e67383a98cf36b21f7cf78a9a44e6301.