Issue 23904006: [Memory] re-suppress old 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 23904006: [Memory] re-suppress old leak (Closed)

Created:
7 years, 3 months ago by groby-ooo-7-16

Modified:
7 years, 3 months ago

Reviewers:
Lei Zhang, benwells

CC:
chromium-reviews, glider+watch_chromium.org, timurrrr+watch_chromium.org, bruening+watch_chromium.org

Base URL:
https://chromium.googlesource.com/chromium/src.git@master

Visibility:
Public.

[Memory] re-suppress old leak Got removed in r218198, reoccured in WebKit memory tests. NOTRY=true TBR=thestig@chromium.org, benwells@chromium.org BUG=241044 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=222101

Created: 7 years, 3 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+9 lines, -0 lines)			Patch
	M	tools/valgrind/memcheck/suppressions.txt	View		1 chunk	+9 lines, -0 lines	0 comments	Download

Total messages: 4 (0 generated)

groby-ooo-7-16

thestig: FYI benwells: You removed the old suppression as redundant - does that mean we ...

7 years, 3 months ago (2013-09-09 21:33:24 UTC) #1

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/groby@chromium.org/23904006/1

7 years, 3 months ago (2013-09-09 21:34:04 UTC) #2

Lei Zhang

7 years, 3 months ago (2013-09-10 23:46:42 UTC) #4

Message was sent while issue was closed.

lgtm, though Blink r157489 seemed to have fixed this. We can probably revert
this soon.