New issue
Advanced search Search tips

Issue 736541 link

Starred by 2 users
Status: Duplicate
Merged: issue 735173
Owner:
mythria@chromium.org
Closed: Jun 2017
Cc:
perezju@chromium.org
primiano@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

v8.runtimestats.browsing_desktop failing on Windows 7

Project Member Reported by martiniss@chromium.org, Jun 23 2017 
v8.runtimestats.browsing_desktop failing on 2 builders

Builders failed on: 
- Win 7 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf
- Win 7 x64 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Win%207%20x64%20Perf

Example swarming tasks: https://chromium-swarm.appspot.com/task?id=36ee1c9107a0c610&refresh=10&show_raw=1 and https://chromium-swarm.appspot.com/task?id=36ee3c9b10839510&refresh=10&show_raw=1

It looks like stories are crashing. It's 2 different stories, and it appears to be flaky. There are minidumps in the test log, which can hopefully be used to debug this.

Comment 1 by mythria@chromium.org, Jun 26 2017 

The failures are only on v8.runtimestats.browse_desktop benchmark on pages pinterest and reddit. The reference build does not fail. The stack trace looks as follows:

002dded0 6cd85f7d 002ddeec 09f499a8 09e07e90 chrome!cc::ResourceProvider::OnMemoryDump+0x190
	002ddfe4 6cd85c03 0e3f0578 09e09d50 6edd8bb0 chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x1dd
	002de0dc 6cd85fde 00000000 09e09d50 0e3f0578 chrome!base::trace_event::MemoryDumpManager::SetupNextMemoryDump+0xc3
	002de1ec 6cd85c03 0e3f0578 0a1b22c0 6edd8bb0 chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x23e
	002de2e4 6cd85fde 00000000 0a1b22c0 0e3f0578 chrome!base::trace_event::MemoryDumpManager::SetupNextMemoryDump+0xc3
	002de3f4 6cd85c03 0e3f0578 09f168b8 6edd8bb0 chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x23e
	002de4ec 6cd85fde 00000000 09f168b8 0e3f0578 chrome!base::trace_event::MemoryDumpManager::SetupNextMemoryDump+0xc3
	002de5fc 6cd85c03 0e3f0578 0a1b2290 6edd8bb0 chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x23e
	002de6f4 6cd85fde 00000000 0a1b2290 0e3f0578 chrome!base::trace_event::MemoryDumpManager::SetupNextMemoryDump+0xc3
	002de804 6cd85c03 0e3f0578 09f167c8 6edd8bb0 chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x23e
	002de8fc 6cd85fde 00000000 09f167c8 0e3f0578 chrome!base::trace_event::MemoryDumpManager::SetupNextMemoryDump+0xc3
	002dea0c 6cd85c03 0e3f0578 09f16978 6edd8bb0 chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x23e
	002deb04 6cd85fde 00000000 09f16978 0e3f0578 chrome!base::trace_event::MemoryDumpManager::SetupNextMemoryDump+0xc3
	002dec14 6cd85c03 0e3f0578 0a1b2350 6edd8bb0 chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x23e
	002ded0c 6cd85fde 00000000 0a1b2350 0e3f0578 chrome!base::trace_event::MemoryDumpManager::SetupNextMemoryDump+0xc3
	002dee1c 6cd85c03 0e3f0578 0a1b2260 6edd8bb0 chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x23e
	002def14 6cd85fde 00000000 002df1d0 0e8043e0 chrome!base::trace_event::MemoryDumpManager::SetupNextMemoryDump+0xc3
	002df020 6cd88161 0e3f0578 002df110 6cdc322c chrome!base::trace_event::MemoryDumpManager::InvokeOnMemoryDump+0x23e
	002df02c 6cdc322c 0e8043e0 00b8cad8 6edd8b2c chrome!base::internal::Invoker<base::internal::BindState<void (__thiscall base::StackSamplingProfiler::SamplingThread::*)(int),base::internal::UnretainedWrapper<base::StackSamplingProfiler::SamplingThread>,int>,void __cdecl(void)>::Run+0x11
	002df110 6cd7d918 6ed6d4d0 002df1d0 ffffffff chrome!base::debug::TaskAnnotator::RunTask+0x20c

Comment 2 by mythria@chromium.org, Jun 26 2017

Cc: primiano@chromium.org perezju@chromium.org
cc'ing memory infra people.

Comment 3 by perezju@chromium.org, Jun 26 2017

Mergedinto: 735173
Status: Duplicate (was: Assigned)
►

Sign in to add a comment