MacSandboxTest tests leak temp folders |
|||||||
Issue description
Chrome Version : 61.0.3150.0
OS Version: OS X 10.12.5
What steps will reproduce the problem?
1. For extra info, something like,
diff --git a/base/files/scoped_temp_dir.cc b/base/files/scoped_temp_dir.cc
index a04e825156b6..e62f5527ac2e 100644
--- a/base/files/scoped_temp_dir.cc
+++ b/base/files/scoped_temp_dir.cc
@@ -21,7 +21,7 @@ ScopedTempDir::ScopedTempDir() {
ScopedTempDir::~ScopedTempDir() {
if (!path_.empty() && !Delete())
- DLOG(WARNING) << "Could not delete temp dir in dtor.";
+ PLOG(WARNING) << "Could not delete temp dir in dtor." << path_.value();
}
bool ScopedTempDir::CreateUniqueTempDir() {
2. run $ content_unittests --gtest_filter=MacSandboxTest.*
What is the expected result?
No warnings about leaked folders
What happens instead of that?
17 leaked tempdirs: `ls -d ${TMPDIR}/.org.chromium.Chromium*`
Output like
[19692:775:0707/153527.880022:975110812416200:WARNING:scoped_temp_dir.cc(24)] Could not delete temp dir in dtor./var/folders/00/1_wbr000h01000cxqpysvccm005bjg/T/.org.chromium.Chromium.hK3uin: Operation not permitted
,
Jul 7 2017
,
Jul 12 2017
,
Nov 8 2017
,
Nov 5
Greg: Just FYI since you're redoing these tests.
,
Nov 5
Indeed I am rewriting those tests completely.
,
Dec 14
Fixed by issue 902597 now?
,
Dec 14
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by tapted@chromium.org
, Jul 7 2017