New issue
Advanced search Search tips

Issue 755625 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

external/wpt/beacon/beacon-error.window.html leaks

Project Member Reported by reillyg@chromium.org, Aug 15 2017

Issue description

This test was imported from WPT in https://chromium-review.googlesource.com/615420 and is failing with a leak in:

https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty%20Leak/builds/8220

I will be adding this test to LeakExpectations. Please investigate this issue as soon as possible.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 15 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fa554869a320faf7983a2392f3b88662f40b0872

commit fa554869a320faf7983a2392f3b88662f40b0872
Author: Reilly Grant <reillyg@chromium.org>
Date: Tue Aug 15 18:42:20 2017

Add leak expectation for new test from WPT

* external/wpt/beacon/beacon-error.window.html

Bug:  755625 
Change-Id: I8ac21f7025eb93039acf5f03e5278014c7491f95
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/614875
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#494463}
[modify] https://crrev.com/fa554869a320faf7983a2392f3b88662f40b0872/third_party/WebKit/LayoutTests/LeakExpectations

Comment 2 by ricea@chromium.org, Nov 10 2017

Confirmed that the leak still happens.
Owner: yhirano@chromium.org
yhirano@, please take a look.
Project Member

Comment 4 by bugdroid1@chromium.org, Feb 15 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/260f8dfb276481e7ee42565e90e3155a126ae0aa

commit 260f8dfb276481e7ee42565e90e3155a126ae0aa
Author: Yutaka Hirano <yhirano@chromium.org>
Date: Thu Feb 15 08:26:24 2018

Let beacon/keepalive tests leak

Requests with keepalive set (including requests initiated by
sendBeacon()) are leaky by design; they are kept alive even when the
frame is detached. This change makes it explicit in LeakExpectations.

Bug:  755625 
Change-Id: I9c708e7f492bb2859bad007faa201e79517f03a2
Reviewed-on: https://chromium-review.googlesource.com/920123
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536967}
[modify] https://crrev.com/260f8dfb276481e7ee42565e90e3155a126ae0aa/third_party/WebKit/LayoutTests/LeakExpectations

Status: WontFix (was: Assigned)
See #4 for reasoning.

Sign in to add a comment