New issue
Advanced search Search tips

Issue 889806 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocking:
issue 836897



Sign in to add a comment

Crash when closing select dropdown

Project Member Reported by bokan@chromium.org, Sep 27

Issue description

Chrome Version: 71.0.3559.6
OS: Linux

What steps will reproduce the problem?
(1) Open a bug in crbug.com
(2) Open any select dropdown
(3) Click on one of the entries to close the popup

What is the expected result?
Nothing

What happens instead?
Crash

I'm running with --enable-blink-gen-property-tree and that's likely the reason. ReportID: 40c25a3812e67041, here's the stack trace:

	0x0000564d97505a6c	(chrome -element_animations.cc:80 )	cc::ElementAnimations::ClearAffectedElementTypes()
0x0000564d974fffac	(chrome -animation_host.cc:164 )	cc::AnimationHost::UnregisterKeyframeEffectForElement(cc::ElementId, cc::KeyframeEffect*)
0x0000564d97503175	(chrome -animation.cc:150 )	cc::Animation::UnregisterKeyframeEffects()
0x0000564d975038ff	(chrome -animation.cc:116 )	cc::Animation::DetachElement()
0x0000564d97505115	(chrome -animation_timeline.cc:122 )	cc::AnimationTimeline::ClearAnimations()
0x0000564d974ff316	(chrome -animation_host.cc:92 )	cc::AnimationHost::ClearMutators()
0x0000564d974ff009	(chrome -animation_host.cc:65 )	cc::AnimationHost::~AnimationHost()
0x0000564d974ff1dd	(chrome -animation_host.cc:62 )	cc::AnimationHost::~AnimationHost()
0x0000564d99caa052	(chrome -memory:2321 )	content::LayerTreeView::~LayerTreeView()
0x0000564d99caa0fd	(chrome -layer_tree_view.cc:150 )	<name omitted>
0x0000564d9a24f58b	(chrome -memory:2321 )	content::RenderWidget::Close()
0x0000564d96225673	(chrome -callback.h:99 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x0000564d96262cc2	(chrome -thread_controller_impl.cc:196 )	base::sequence_manager::internal::ThreadControllerImpl::DoWork(base::sequence_manager::internal::ThreadControllerImpl::WorkType)
0x0000564d96225673	(chrome -callback.h:99 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x0000564d96224298	(chrome -message_loop.cc:434 )	base::MessageLoop::RunTask(base::PendingTask*)
0x0000564d9622476f	(chrome -message_loop.cc:445 )	base::MessageLoop::DoWork()
0x0000564d96226ae4	(chrome -message_pump_default.cc:37 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
0x0000564d96244c93	(chrome -run_loop.cc:102 )	<name omitted>
0x0000564d9a280b9a	(chrome -renderer_main.cc:202 )	content::RendererMain(content::MainFunctionParams const&)
0x0000564d95eb853b	(chrome -content_main_runner_impl.cc:496 )	content::ContentMainRunnerImpl::Run(bool)
0x0000564d95eee3a4	(chrome -main.cc:472 )	service_manager::Main(service_manager::MainParams const&)
0x0000564d95eb67d0	(chrome -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const&)
0x0000564d94146652	(chrome -chrome_main.cc:102 )	ChromeMain
0x00007f47738862b0	(libc-2.24.so + 0x000202b0 )	
 
Labels: -Pri-3 Pri-2
Status: Available (was: Untriaged)
flackr@: is this the same as the gmail crash that you mentioned?
Labels: Stability-Crash
Owner: pdr@chromium.org
Status: Assigned (was: Available)
Blocking: 836897
Owner: flackr@chromium.org
Mergedinto: 892068
Status: Duplicate (was: Assigned)
Issue 892068 seems to have been this crash, and it is now resolved.

Sign in to add a comment