New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 698282 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

MemoryCoordinatorImpl tests are flaky

Project Member Reported by dimaa@chromium.org, Mar 3 2017

Issue description

MemoryCoordinatorImpl tests fails on first time and need to be re-run separately.
 
Description: Show this description
Status: Started (was: Untriaged)
Project Member

Comment 3 by bugdroid1@chromium.org, Mar 6 2017

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

commit aba30978d6c58a937eb2cf5fbdcde3e2abb7cfaa
Author: dimaa <dimaa@chromium.org>
Date: Mon Mar 06 19:57:12 2017

Clean up g_memory_coordinator after each MemoryCoordinatorImpl test

MemoryCoordinatorImpl tests fail the first time and should be re-run separately.
g_memory_coordinator need to be cleaned up between tests, otherwise the subsequent tests
will crash trying to reset g_memory_coordinator.

This CL implements reset method which called after each MemoryCoordinatorImpl in destructor.

BUG=698282

Review-Url: https://codereview.chromium.org/2726983006
Cr-Commit-Position: refs/heads/master@{#454926}

[modify] https://crrev.com/aba30978d6c58a937eb2cf5fbdcde3e2abb7cfaa/base/memory/memory_coordinator_proxy.cc
[modify] https://crrev.com/aba30978d6c58a937eb2cf5fbdcde3e2abb7cfaa/content/browser/memory/memory_coordinator_impl.cc

Sign in to add a comment