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

Issue 765140 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug
Hotlist-MemoryInfra



Sign in to add a comment

BenchmarkSmokeTest.tracing.tracing_with_background_memory_infra is flaky

Project Member Reported by primiano@chromium.org, Sep 14 2017

Issue description

The catapult autoroller has been failing on this roll
https://chromium-review.googlesource.com/c/chromium/src/+/666049

On this task:
https://chromium-swarm.appspot.com/task?id=3898b27dc84cff10&refresh=10&show_raw=1

With this error:
  	ATTENTION: default value of option force_s3tc_enable overridden by environment.
  	[17905:17905:0914/031455.448212:ERROR:sandbox_linux.cc(346)] InitializeSandbox() called with multiple threads in process gpu-process.
  	[17850:17880:0914/031456.318422:FATAL:process_memory_dump.cc(475)] Check failed: is_black_hole_non_fatal_for_testing_. 
  	#0 0x7fca21bba107 base::debug::StackTrace::StackTrace()
  	#1 0x7fca21bd3e01 logging::LogMessage::~LogMessage()
  	#2 0x7fca21c3e4e3 base::trace_event::ProcessMemoryDump::GetBlackHoleMad()
  	#3 0x7fca205858ca content::LocalStorageContextMojo::OnMemoryDump()
  	#4 0x7fca21c399c7 base::trace_event::MemoryDumpManager::InvokeOnMemoryDump()

Lalit told me that this is related with  Issue 762639  and should be fixed by https://chromium-review.googlesource.com/c/chromium/src/+/657383 .

I'll temporarily disable the test, as it's blocking the catapult autoroller, please reenable after the change above lands

 
Project Member

Comment 2 by bugdroid1@chromium.org, Sep 14 2017

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

commit 07fba2e66d74a1ac81725edd7888612c89d7b750
Author: Primiano Tucci <primiano@chromium.org>
Date: Thu Sep 14 12:16:36 2017

telemetry: disable TracingWithBackgroundMemoryInfra

It is flaky and causes catapult roller issues, see attached bug.

TBR=nednguyen@google.com,sullivan@chromium.org,ssid@chromium.org

Bug:  765140 
Change-Id: I1298046d2cd0697c192d1953484f3d1c4b5d1c4f
Reviewed-on: https://chromium-review.googlesource.com/666917
Commit-Queue: Primiano Tucci <primiano@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501929}
[modify] https://crrev.com/07fba2e66d74a1ac81725edd7888612c89d7b750/tools/perf/benchmarks/tracing.py

Project Member

Comment 3 by bugdroid1@chromium.org, Sep 27 2017

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

commit 7b38e13d24ab64a93e41f307bbf2659371e221ae
Author: Lalit Maganti <lalitm@chromium.org>
Date: Wed Sep 27 10:58:42 2017

Revert "telemetry: disable TracingWithBackgroundMemoryInfra"

This reverts commit 07fba2e66d74a1ac81725edd7888612c89d7b750.

Reason for revert: This should now be fixed given that https://chromium-review.googlesource.com/c/chromium/src/+/657383 has now landed.

Original change's description:
> telemetry: disable TracingWithBackgroundMemoryInfra
> 
> It is flaky and causes catapult roller issues, see attached bug.
> 
> TBR=nednguyen@google.com,sullivan@chromium.org,ssid@chromium.org
> 
> Bug:  765140 
> Change-Id: I1298046d2cd0697c192d1953484f3d1c4b5d1c4f
> Reviewed-on: https://chromium-review.googlesource.com/666917
> Commit-Queue: Primiano Tucci <primiano@chromium.org>
> Reviewed-by: Ned Nguyen <nednguyen@google.com>
> Reviewed-by: Primiano Tucci <primiano@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#501929}

Bug:  765140 
Change-Id: Ife9eb9e1f6f5514e24a816455899707e03467743
Reviewed-on: https://chromium-review.googlesource.com/682037
Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Commit-Queue: Lalit Maganti <lalitm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#504624}
[modify] https://crrev.com/7b38e13d24ab64a93e41f307bbf2659371e221ae/tools/perf/benchmarks/tracing.py

Comment 4 by lalitm@chromium.org, Sep 27 2017

Status: Fixed (was: Assigned)
Issue now fixed and test reenabled.

Sign in to add a comment