Issue metadata
Sign in to add a comment
|
[stablechannel] followtheemeraldstar.com crashes on Chrome desktop |
||||||||||||||||||||||||
Issue descriptionChrome Version: 65.0.3325.181 OS: Linux What steps will reproduce the problem? (1) Open https://www.followtheemeraldstar.com What is the expected result? Chrome doesn't crash What happens instead? Chrome tab crashes almost immediately
,
Apr 3 2018
Crash ID: c88a3968aed13f25 Client ID: AECnTLmkvZQ6UxnYPW9Mtt3mD0xTAnc+Iw==
,
Apr 3 2018
Stack trace from the crash looks like an OOM condition: 0x00007f6a379fa4f9 (libc-2.24.so + 0x000344f9 ) 0x000055ae3aeb62fc (chrome -logging.cc:842 ) logging::LogMessage::~LogMessage() 0x000055ae3aed7431 (chrome -memory_linux.cc:36 ) base::(anonymous namespace)::OnNoMemory() 0x000055ae3af32ac1 (chrome -allocator_shim.cc:60 ) GlibcMallocHook 0x000055ae3a35e54d (chrome -allocation.cc:101 ) v8::internal::AllocWithRetry(unsigned long) 0x000055ae3a95edbd (chrome -accounting-allocator.cc:87 ) v8::internal::AccountingAllocator::GetSegment(unsigned long) 0x000055ae3a95f0ed (chrome -zone.cc:118 ) v8::internal::Zone::New(unsigned long) 0x000055ae3a490505 (chrome -zone.h:53 ) v8::internal::compiler::InstructionSequence::AddImmediate(v8::internal::compiler::Constant const&) 0x000055ae3a486ece (chrome -instruction-selector-impl.h ) v8::internal::compiler::InstructionSelector::AddOperandToStateValueDescriptor(v8::internal::compiler::StateValueList*, v8::internal::ZoneVector<v8::internal::compiler::InstructionOperand>*, v8::internal::compiler::OperandGenerator*, v8::internal::compiler::StateObjectDeduplicator*, v8::internal::compiler::Node*, v8::internal::MachineType, v8::internal::compiler::FrameStateInputKind, v8::internal::Zone*) 0x000055ae3a487cf9 (chrome -instruction-selector.cc:636 ) v8::internal::compiler::InstructionSelector::AddInputsToFrameStateDescriptor(v8::internal::compiler::FrameStateDescriptor*, v8::internal::compiler::Node*, v8::internal::compiler::OperandGenerator*, v8::internal::compiler::StateObjectDeduplicator*, v8::internal::ZoneVector<v8::internal::compiler::InstructionOperand>*, v8::internal::compiler::FrameStateInputKind, v8::internal::Zone*) 0x000055ae3a490390 (chrome -instruction-selector.cc:2577 ) v8::internal::compiler::InstructionSelector::EmitDeoptimize(int, unsigned long, v8::internal::compiler::InstructionOperand*, unsigned long, v8::internal::compiler::InstructionOperand*, v8::internal::DeoptimizeKind, v8::internal::DeoptimizeReason, v8::internal::VectorSlotPair const&, v8::internal::compiler::Node*) 0x000055ae3a984597 (chrome -instruction-selector-x64.cc:1528 ) v8::internal::compiler::(anonymous namespace)::VisitCompareWithMemoryOperand(v8::internal::compiler::InstructionSelector*, int, v8::internal::compiler::Node*, v8::internal::compiler::InstructionOperand, v8::internal::compiler::FlagsContinuation*) 0x000055ae3a97c12e (chrome -instruction-selector-x64.cc ) v8::internal::compiler::(anonymous namespace)::VisitWordCompare(v8::internal::compiler::InstructionSelector*, v8::internal::compiler::Node*, int, v8::internal::compiler::FlagsContinuation*) 0x000055ae3a97c915 (chrome -instruction-selector-x64.cc:1752 ) v8::internal::compiler::(anonymous namespace)::VisitWord64Compare(v8::internal::compiler::InstructionSelector*, v8::internal::compiler::Node*, v8::internal::compiler::FlagsContinuation*) 0x000055ae3a97b2fd (chrome -instruction-selector-x64.cc ) v8::internal::compiler::(anonymous namespace)::VisitWordCompareZero(v8::internal::compiler::InstructionSelector*, v8::internal::compiler::Node*, v8::internal::compiler::Node*, v8::internal::compiler::FlagsContinuation*) 0x000055ae3a97b9fb (chrome -instruction-selector-x64.cc:1950 ) v8::internal::compiler::InstructionSelector::VisitDeoptimizeUnless(v8::internal::compiler::Node*) 0x000055ae3a485dd4 (chrome -instruction-selector.cc:947 ) v8::internal::compiler::InstructionSelector::SelectInstructions() 0x000055ae3a520b72 (chrome -pipeline.cc:1538 ) v8::internal::compiler::PipelineImpl::SelectInstructions(v8::internal::compiler::Linkage*) 0x000055ae3a51ef41 (chrome -pipeline.cc:1948 ) v8::internal::compiler::PipelineImpl::OptimizeGraph(v8::internal::compiler::Linkage*) 0x000055ae3a51d31f (chrome -pipeline.cc:820 ) v8::internal::compiler::PipelineCompilationJob::ExecuteJobImpl() 0x000055ae3a432554 (chrome -compiler.cc:110 ) <name omitted> 0x000055ae3a430df8 (chrome -optimizing-compile-dispatcher.cc:115 ) v8::internal::OptimizingCompileDispatcher::CompileNext(v8::internal::CompilationJob*) 0x000055ae3a43227b (chrome -optimizing-compile-dispatcher.cc:67 ) v8::internal::OptimizingCompileDispatcher::CompileTask::RunInternal() 0x000055ae3aea0a4e (chrome -callback.h:65 ) base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) 0x000055ae3aef9a21 (chrome -task_tracker.cc:420 ) base::internal::TaskTracker::RunOrSkipTask(base::internal::Task, base::internal::Sequence*, bool) 0x000055ae3aef9fb2 (chrome -task_tracker_posix.cc:23 ) base::internal::TaskTrackerPosix::RunOrSkipTask(base::internal::Task, base::internal::Sequence*, bool) 0x000055ae3aef8fa8 (chrome -task_tracker.cc:322 ) base::internal::TaskTracker::RunNextTask(scoped_refptr<base::internal::Sequence>, base::internal::CanScheduleSequenceObserver*) 0x000055ae3aef4c23 (chrome -scheduler_worker.cc:72 ) base::internal::SchedulerWorker::Thread::ThreadMain() 0x000055ae3af024f2 (chrome -platform_thread_posix.cc:75 ) base::(anonymous namespace)::ThreadFunc(void*) 0x00007f6a3d93b493 (libpthread-2.24.so + 0x00007493 )
,
Apr 3 2018
Users experienced this crash on the following builds: Linux Dev 67.0.3381.0 - 22.64 CPM, 79 reports, 26 clients (signature Out of Memory (v8)) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Apr 4 2018
Users experienced this crash on the following builds: Linux Beta 66.0.3359.66 - 19.72 CPM, 143 reports, 57 clients (signature Out of Memory (v8)) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Apr 5 2018
This crash has high impact on Chrome's stability. Signature: Out of Memory (v8). Channel: beta. Platform: linux. Labeling issue 827627 with ReleaseBlock-Stable. If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Apr 5 2018
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 6 2018
Unable to reproduce this issue on Ubuntu 14.04 using chrome latest stable #65.0.3325.181 by following steps mentioned in the original comment. According to the crash server this crash is ranked as number #1 under renderer process for windows platform. As of now observing 57 client ID's with 80 crash instances. Link to list of the builds: ---------------------------- https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Mac%27%20AND%20expanded_custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27Out%20of%20Memory%20(v8)%27#-samplereports,productversion:1000,-magicsignature:50,-magicsignature2:50,-stablesignature:50,-magicsignaturesorted:50 Thanks!
,
Apr 9 2018
I can't reproduce either with the URL in #0, but #8 says it's still reported. From stack, it looks like v8 compiler hits oom?
,
Apr 9 2018
I can repro this 100% on my gLinux desktop, through my personal profile as well as a new profile I setup. Restarting chrome makes no difference. On my pixelbook, however, the site loads successfully.
,
Apr 9 2018
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 10 2018
I would assume this is simply a normal OOM, so nothing to fix on our end. Memory sheriff, please confirm.
,
Apr 12 2018
How do you reproduce the issue? Can you create a heap snapshot before OOM triggers?
,
Apr 12 2018
https://webgis.dor.wa.gov/taxratelookup/SalesTax.aspx this reproduces 100% of the time in 66.0.3359.81
,
Apr 13 2018
Issue 832002 has been merged into this issue.
,
Apr 16 2018
Issue 833086 has been merged into this issue.
,
Apr 24 2018
Issue 835771 has been merged into this issue.
,
Apr 24 2018
Can we get this bisected since there is a manual repro. +Rajshree.
,
Apr 25 2018
Unable to reproduce the issue on ubuntu 14.04 desktop and 17.10 laptop using chrome reported version #65.0.3325.181 and latest stable #66.0.3359.117. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Opened https://www.followtheemeraldstar.com as per comment #0 and opened https://webgis.dor.wa.gov/taxratelookup/SalesTax.aspx as per comment #14 in chrome. 2. Observed that chrome did not crash as expected. seanpaul@ - Could you please check the issue on latest stable #66.0.3359.117 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Apr 25 2018
@c19: It reproduces on 66.0.3359.117 in a fresh profile with only corp extensions installed.
,
May 2 2018
Unable to reproduce the issue on ubuntu 14.04 desktop and 17.10 laptop using chrome reported version #65.0.3325.181 and latest stable #66.0.3359.139. As per comment #19, it seems that the issue reproduces using only corp extensions installed. Hence, forwarding the issue to inhouse team for further triaging of the issue. Thanks...!!
,
May 2 2018
,
May 3 2018
Interesting, the OOM is in the heap setup. Digging into this now.
,
May 3 2018
The process starts a lot of workers and runs out of virtual address space.
,
May 3 2018
FYI: We will land a mitigation that will allow more workers shortly.
,
May 4 2018
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/6b1457cfd6baa332ffa968b74fff705bac72e762 commit 6b1457cfd6baa332ffa968b74fff705bac72e762 Author: Hannes Payer <hpayer@chromium.org> Date: Fri May 04 13:47:09 2018 Reduce maximal code range size to 128M on Linux, Windows, and OSX for x64 and ia32. Bug: chromium:800348 , chromium:827627 , chromium:839750 Change-Id: I112e20b83eb1937476ebb4f30cf5679113759c0c Reviewed-on: https://chromium-review.googlesource.com/1044195 Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#52996} [modify] https://crrev.com/6b1457cfd6baa332ffa968b74fff705bac72e762/src/globals.h |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by junov@chromium.org
, Apr 3 2018