Issue metadata
Sign in to add a comment
|
CHECK: !map->is_stable() in v8/src/compiler/access-info.cc |
||||||||||||||||||||||||
Issue descriptionFatal error crashes the tab in a tip of tree Release build on Linux occurred after loading chrome://settings/fonts. The crash occurs often but not always. 1. Visit chrome://settings/fonts 2. If crash didn't occur, refresh until it does # # Fatal error in ../../v8/src/compiler/access-info.cc, line 278 # Check failed: !map->is_stable(). # #0 0x5602e6d5df97 base::debug::StackTrace::StackTrace() #1 0x5602e938c1f5 gin::(anonymous namespace)::PrintStackTrace() #2 0x5602e924565d V8_Fatal #3 0x5602e5f9a0d2 v8::internal::compiler::AccessInfoFactory::ComputeElementAccessInfos() #4 0x5602e6049b44 v8::internal::compiler::JSNativeContextSpecialization::ReduceElementAccess() #5 0x5602e604c5df v8::internal::compiler::JSNativeContextSpecialization::ReduceKeyedAccess<>() #6 0x5602e60443da v8::internal::compiler::JSNativeContextSpecialization::ReduceJSLoadProperty() #7 0x5602e5ffa702 v8::internal::compiler::GraphReducer::ReduceTop() #8 0x5602e5ffa0e8 v8::internal::compiler::GraphReducer::ReduceNode() #9 0x5602e60a35dc v8::internal::compiler::InliningPhase::Run() #10 0x5602e609c836 v8::internal::compiler::PipelineImpl::CreateGraph() #11 0x5602e609c2ba v8::internal::compiler::PipelineCompilationJob::PrepareJobImpl() #12 0x5602e5f8c87d v8::internal::CompilationJob::PrepareJob() #13 0x5602e5f905de v8::internal::(anonymous namespace)::GetOptimizedCode() #14 0x5602e5f8f371 v8::internal::Compiler::CompileOptimized() #15 0x5602e64e0185 v8::internal::__RT_impl_Runtime_CompileOptimized_Concurrent() #16 0x3cac57904564 <unknown>
,
May 16 2017
,
May 16 2017
(because I found this https://chromium.googlesource.com/v8/v8.git/+/2d856544e5e3cb8abf99a30749b4bfe39c29886a)
,
May 17 2017
,
May 17 2017
Michael, can you find a good owner for this bug?
,
May 17 2017
cbruni@: why did you unassign this issue? perhaps you can give an explanation next time as well? it certainly seems like the DCHECK() being tripped was added here by ishell@: https://chromium-review.googlesource.com/c/483442/6/src/compiler/access-info.cc
,
May 17 2017
Yes, I'm sure it's a dupe of issue 723455 . The repro may be different in this particular case but the fix just makes the compilers properly handle such a "bad" case. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dbeam@chromium.org
, May 16 2017