Issue metadata
Sign in to add a comment
|
ContentSettingBubbleModelMixedScriptOopifTest.MixedContentInCrossSiteIframe is Flaky |
||||||||||||||||||||||
Issue descriptionCurrently ContentSettingBubbleModelMixedScriptOopifTest.MixedContentInCrossSiteIframe is flaking on win7_chromium_rel_ng. With the following DCHECK failure: FATAL:PaintLayer.cpp(1888)] Check failed: GetLayoutObject().GetDocument().Lifecycle().GetState() >= DocumentLifecycle::kCompositingClean. Backtrace: base::debug::StackTrace::StackTrace [0x024CB300+32] base::debug::StackTrace::StackTrace [0x0248BD2D+13] logging::LogMessage::~LogMessage [0x02437090+80] blink::PaintLayer::HitTestLayer [0x05065063+105] blink::PaintLayer::HitTest [0x05064EE6+376] blink::LayoutView::HitTestNoLifecycleUpdate [0x04F4FA43+255] blink::LayoutView::HitTest [0x04F4F808+48] blink::EventHandler::HitTestResultAtPoint [0x04DFD11F+473] blink::WebFrameWidgetImpl::HitTestResultForRootFramePos [0x05E3D360+150] blink::WebFrameWidgetImpl::CoreHitTestResultAt [0x05E3BD25+197] blink::WebFrameWidgetImpl::HitTestResultAt [0x05E3BC39+41] content::RenderWidgetInputHandler::GetFrameSinkIdAtPoint [0x05506BA3+157] content::RenderWidget::GetFrameSinkIdAtPoint [0x0544E48C+22] content::InputTargetClientImpl::FrameSinkIdAt [0x0544586B+43] viz::mojom::InputTargetClientStubDispatch::AcceptWithResponder [0x01010D48+258] viz::mojom::InputTargetClientStub<mojo::RawPtrImplRefTraits<viz::mojom::InputTargetClient> >::AcceptWithResponder [0x0544590E+62] mojo::InterfaceEndpointClient::HandleValidatedMessage [0x0304C943+539] mojo::FilterChain::Accept [0x03050303+131] mojo::InterfaceEndpointClient::HandleIncomingMessage [0x0304D718+106] mojo::internal::MultiplexRouter::ProcessIncomingMessage [0x03046632+698] mojo::internal::MultiplexRouter::Accept [0x030461B7+295] mojo::FilterChain::Accept [0x03050303+131] mojo::Connector::ReadSingleMessage [0x0304B9FB+367] mojo::Connector::ReadAllAvailableMessages [0x0304C0D9+87] mojo::Connector::OnHandleReadyInternal [0x0304BFA4+126] base::internal::Invoker<base::internal::BindState<void (__thiscall update_client::TaskUpdate::*)(enum update_client::Error),base::internal::UnretainedWrapper<update_client::TaskUpdate> >,void __cdecl(enum update_client::Error)>::RunOnce [0x010918EF+15] favicon::FaviconService::FaviconResultsCallbackRunner [0x03CC3BA8+24] base::internal::Invoker<base::internal::BindState<bool (__cdecl*)(GURL const &,content::WebContents *,navigation_interception::NavigationParams const &),GURL>,bool __cdecl(content::WebContents *,navigation_interception::NavigationParams const &)>::Run [0x0592F0C3+19] mojo::SimpleWatcher::OnHandleReady [0x030578E0+224] base::internal::Invoker<base::internal::BindState<void (__thiscall mojo::SimpleWatcher::*)(int,unsigned int,mojo::HandleSignalsState const &),base::WeakPtr<mojo::SimpleWatcher>,int,unsigned int,mojo::HandleSignalsState>,void __cdecl(void)>::Run [0x03057B6A+58] base::debug::TaskAnnotator::RunTask [0x024C86E7+231] blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue [0x0230D699+441] blink::scheduler::TaskQueueManager::DoWork [0x0230D1A9+553] base::internal::Invoker<base::internal::BindState<void (__thiscall content::VideoCaptureHost::*)(int),base::WeakPtr<content::VideoCaptureHost>,int>,void __cdecl(void)>::RunOnce [0x027755DB+59] base::debug::TaskAnnotator::RunTask [0x024C86E7+231] blink::scheduler::internal::ThreadControllerImpl::DoWork [0x023119B5+197] base::internal::Invoker<base::internal::BindState<void (__thiscall content::VideoEncoderShim::*)(enum media::VideoEncodeAccelerator::Error),base::WeakPtr<content::VideoEncoderShim>,enum media::VideoEncodeAccelerator::Error>,void __cdecl(void)>::RunOnce [0x04598321+49] base::debug::TaskAnnotator::RunTask [0x024C86E7+231] base::internal::IncomingTaskQueue::RunTask [0x024E5259+105] base::MessageLoop::RunTask [0x02464617+519] base::MessageLoop::DeferOrRunPendingTask [0x02464980+160] base::MessageLoop::DoWork [0x02464BC8+520] base::MessagePumpDefault::Run [0x024E8BA1+177] base::MessageLoop::Run [0x02463FB9+169] base::RunLoop::Run [0x0244540C+204] content::RendererMain [0x05419E55+501] content::RunNamedProcessTypeMain [0x02408ABC+148] content::ContentMainRunnerImpl::Run [0x02409028+280] service_manager::Main [0x039DE555+677] content::ContentMain [0x024089CF+51] content::LaunchTests [0x025A6644+284] LaunchChromeTests [0x0581A5E9+257] main [0x0581A1C3+111] __scrt_common_main_seh [0x063098BA+248] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:283) BaseThreadInitThunk [0x74D8336A+18] RtlInitializeExceptionChain [0x77189902+99] RtlInitializeExceptionChain [0x771898D5+54] Example failing build: https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/81208
,
Jan 16 2018
,
Jan 16 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/770b7c3deac4273611f32f1493e1638fbcb9b6ce commit 770b7c3deac4273611f32f1493e1638fbcb9b6ce Author: Jonathan <jonross@chromium.org> Date: Tue Jan 16 17:10:12 2018 Disable a flaking ContentSettingBubbleModelMixedScriptOopifTest Currently ContentSettingBubbleModelMixedScriptOopifTest.MixedContentInCrossSiteIframe is flaking, preventing changes from landing. This disables the test while a fix is investigated TBR=msramek@chromium.org TEST=ContentSettingBubbleModelMixedScriptOopifTest.MixedContentInCrossSiteIframe Bug: 802281 Change-Id: I0fbffbb77215b038d6192f72929c9258ee70a030 Reviewed-on: https://chromium-review.googlesource.com/868630 Commit-Queue: Jonathan Ross <jonross@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#529451} [modify] https://crrev.com/770b7c3deac4273611f32f1493e1638fbcb9b6ce/chrome/browser/ui/content_settings/content_setting_bubble_model_browsertest.cc
,
Jan 16 2018
Issue 802345 has been merged into this issue.
,
Jan 22 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/cacd0085c363f70055d6a20a51ad670a1681c411 commit cacd0085c363f70055d6a20a51ad670a1681c411 Author: Ken Buchanan <kenrb@chromium.org> Date: Mon Jan 22 20:38:12 2018 Re-enable various SitePerProcessBrowserTests A bug that was causing flakes in many OOPIF-based browser tests was fixed in r530669. This re-enables several tests that were disabled due to that bug. TBR=msramek@chromium.org Bug: 798476 , 803641 , 803628 , 803627 , 802828 , 802281 Change-Id: Ib37c6761cd1ee46d8e49ef393db21209935862dd Reviewed-on: https://chromium-review.googlesource.com/879101 Commit-Queue: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#530981} [modify] https://crrev.com/cacd0085c363f70055d6a20a51ad670a1681c411/chrome/browser/ui/content_settings/content_setting_bubble_model_browsertest.cc [modify] https://crrev.com/cacd0085c363f70055d6a20a51ad670a1681c411/content/browser/site_per_process_browsertest.cc |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nasko@chromium.org
, Jan 16 2018Owner: kenrb@chromium.org