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

Issue 622353 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

smoothness.key_desktop_move_cases failure on Win 7 Perf (2) at 401238:401252

Project Member Reported by petrcermak@chromium.org, Jun 22 2016

Issue description

Revision range first seen: r401238:r401252
Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf%20%282%29/builds/12243/steps/smoothness.key_desktop_move_cases/logs/stdio

It seems that the failure is due to a native crash in V8 GC:

ChildEBP RetAddr  
WARNING: Frame IP not in any known module. Following frames may be wrong.
0015d5ac 65489ba8 0x0
0015d608 654894c8 chrome_child!v8::internal::SlotSet::Iterate<<lambda_91337496e4f404b0eb3fec61908913c5> >+0x108
0015d654 6547ce15 chrome_child!v8::internal::RememberedSet<1>::IterateMemoryChunks<<lambda_b3c32a862b42237c31f6951befa3fdd0> >+0xa8
0015d830 6547bfe1 chrome_child!v8::internal::Heap::Scavenge+0x3d5
0015d918 6547b3df chrome_child!v8::internal::Heap::PerformGarbageCollection+0x2e1
0015d988 6545a85e chrome_child!v8::internal::Heap::CollectGarbage+0x16f
0015d9c0 655da24a chrome_child!v8::internal::Factory::NewFillerObject+0xee
0015da9c 655eb14e chrome_child!v8::internal::Runtime_AllocateInTargetSpace+0xea
0015daa0 2ddbf5ed chrome_child!v8::internal::Runtime_KeyedGetProperty+0x6e
0015daa4 109fffd1 0x2ddbf5ed
0015daa8 2ddc6649 0x109fffd1
0015daac 2ddcb575 0x2ddc6649
0015dab0 0015db14 0x2ddcb575
0015dab4 13afc01b 0x15db14
0015db14 30b7fc8a 0x13afc01b
0015dbe4 1940b516 0x30b7fc8a
0015dc04 30b7b8af 0x1940b516
0015dcb8 29e7b488 0x30b7b8af
0015dce0 29e79019 0x29e7b488
0015dde8 655e8c0c 0x29e79019
0015ddec 0015de88 chrome_child!v8::internal::Runtime::GetObjectProperty+0x27c
0015ddf0 0015de84 0x15de88
0015de88 1370819d 0x15de84
0015de8c 38ec87c5 0x1370819d
0015de90 1370819d 0x38ec87c5
0015de94 00000000 0x1370819d

There were 2 V8 rolls in the revision range:

https://codereview.chromium.org/2083243003 -> https://chromium.googlesource.com/v8/v8/+log/4f1b295d..4e627b31
https://codereview.chromium.org/2086263002 -> https://chromium.googlesource.com/v8/v8/+log/4e627b31..2254a8bd

bmeurer: You had the most changes in the two V8 rolls. Is there any chance any of them could have caused this? If not (and this is not just a flake), I'll kick off a bisect.

If the test is disabled, please downgrade to Pri-2.

 
Cc: mlippautz@chromium.org hpayer@chromium.org u...@chromium.org
Doesn't seem to be related to any of my CLs (actually the two ranges look pretty harmless overall); maybe just flushing out some bug. Adding some GC folks.
Owner: jarin@chromium.org
Assigning to memory sheriff.
Status: Assigned (was: Untriaged)
Friendly sheriff ping

(According to the Perf Bot Sheriffing guide, Pri-1 build bot bugs should be pinged daily. Please close the issue if it's already been fixed.)

Comment 4 by jarin@chromium.org, Jun 28 2016

petrcermak, could you kick off a bisect, then?

I looked at the CLs in the range and nothing looks related.
Status: WontFix (was: Assigned)
The failure doesn't happen anymore, so I think we should mark this as WontFix.

Sign in to add a comment