Status: Accepted
Owner: ----
Labels: Type-Bug Priority-Medium
New issue 3728 by [email protected]: CHECK(idle_time_in_ms > 0) failed,
src\heap\gc-idle-time-handler.cc, line 66
https://code.google.com/p/v8/issues/detail?id=3728
This assertion failure just started showing up on all of the debug GPU
bots. The probable reason it wasn't caught by the tryservers is that
dcheck_always_on=1, which the GPU bots set, isn't honored by V8's build
system. This should be filed separately; I'd appreciate it if someone from
the V8 team could take care of that.
There's no good stack trace but is what is available:
#
# Fatal error in
c:\b\build\slave\gpu_win_builder__dbg_\build\src\v8\src\heap\gc-idle-time-handler.cc,
line 66
# CHECK(idle_time_in_ms > 0) failed
#
Stack Trace:
********************************************************************************
ChildEBP RetAddr
WARNING: Frame IP not in any known module. Following frames may be wrong.
0018ec60 0ab3d08d 0x0
*** WARNING: Unable to verify checksum for cc.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
cc.dll -
0018ee80 0ea2acf3 v8!v8::String::Value::operator*+0x3efd
0018ee90 0eac00bf
cc!cc::LayerTreeHostImpl::CreateLatencyInfoSwapPromiseMonitor+0x3c5fba
0018f0dc 0eac9307
cc!cc::LayerTreeHostImpl::CreateLatencyInfoSwapPromiseMonitor+0x45b386
0018f0f0 0eac6672
cc!cc::LayerTreeHostImpl::CreateLatencyInfoSwapPromiseMonitor+0x4645ce
0018f104 0eac88c5
cc!cc::LayerTreeHostImpl::CreateLatencyInfoSwapPromiseMonitor+0x461939
*** WARNING: Unable to verify checksum for base.dll
0018f134 015d582f
cc!cc::LayerTreeHostImpl::CreateLatencyInfoSwapPromiseMonitor+0x463b8c
0018f14c 01600e0b base!base::Callback<void __cdecl(void)>::Run+0x2f
0018f214 016bd92d base!base::debug::TaskAnnotator::RunTask+0x22b
0018f3e0 016bb034 base!base::MessageLoop::RunTask+0x1ed
0018f3f0 016bb6bd base!base::MessageLoop::DeferOrRunPendingTask+0x34
0018f450 016c23d4 base!base::MessageLoop::DoWork+0xdd
0018f560 016bd6d7 base!base::MessagePumpDefault::Run+0xf4
0018f638 017299a6 base!base::MessageLoop::RunHandler+0xf7
0018f66c 016bd57b base!base::RunLoop::Run+0x46
*** WARNING: Unable to verify checksum for content.dll
0018f6a0 12033e67 base!base::MessageLoop::Run+0x2b
0018fa30 10998049 content!content::RendererMain+0x547
0018fb04 10997e62 content!content::RunNamedProcessTypeMain+0xa9
0018fd00 10982090 content!content::ContentMainRunnerImpl::Run+0x242
*** WARNING: Unable to verify checksum for chrome.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
chrome.dll -
0018fd30 03027598 content!content::ContentMain+0x90
0018fd90 00413fa3
chrome_2b10000!policy::internal::RestrictionNode::operator=+0x2b7e4b
0018feb0 00411538 chrome!MainDllLoader::Launch+0x3c3
0018ff1c 004be0ec chrome!wWinMain+0xb8
0018ff80 004be22d chrome!__tmainCRTStartup+0x21c
0018ff88 7660338a chrome!wWinMainCRTStartup+0xd
0018ff94 77d6bf32 kernel32!BaseThreadInitThunk+0x12
0018ffd4 77d6bf05 ntdll!RtlInitializeExceptionChain+0x63
0018ffec 00000000 ntdll!RtlInitializeExceptionChain+0x36
********************************************************************************
First failing builds on several builders:
http://build.chromium.org/p/chromium.gpu/builders/Win7%20Debug%20%28NVIDIA%29/builds/24892
http://build.chromium.org/p/chromium.gpu/builders/Mac%20Debug%20%28Intel%29/builds/39689
http://build.chromium.org/p/chromium.gpu/builders/Mac%20Retina%20Debug/builds/28422
http://build.chromium.org/p/chromium.gpu/builders/Linux%20Debug%20%28NVIDIA%29/builds/37562
The fault is almost certainly the V8 roll at
https://codereview.chromium.org/770503002 which I am going to revert.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
