New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 801338 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 667551
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

iframe-script-modify-attr.html fails with site-per-process. Check failed: 0 != snapshot.info().width()

Project Member Reported by maxlg@google.com, Jan 11 2018

Issue description

Chrome Version: not sure how to determine it on try server
OS: 'Ubuntu-14.04'

I encountered this crash while I was dry-running an probably unrelated CL (at least no clear relationship to me). It's not reproducible on my local computer. But it might be nice to record the crash.


What steps will reproduce the problem?
(1) Run layout test: iframe-script-modify-attr.html 

What is the expected result?
The test should pass.

What happens instead?
The test report shows that content shell crashes

More info:
Layout test failure reports:
https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/622372

Try server log page:
https://storage.googleapis.com/chromium-layout-test-archives/linux_chromium_rel_ng/622372/site_per_process_webkit_layout_tests%20%28with%20patch%29/layout-test-results/results.html


Please use labels and text to provide additional information.

======================================================================
crash log for renderer (pid <unknown>):
STDOUT: layer at (0,0) size 800x600
STDOUT:   LayoutView at (0,0) size 800x600
STDOUT: layer at (0,0) size 800x225
STDOUT:   LayoutBlockFlow {HTML} at (0,0) size 800x225
STDOUT:     LayoutBlockFlow {BODY} at (8,8) size 784x209
STDOUT:       LayoutText {#text} at (0,0) size 0x0
STDOUT: layer at (8,8) size 204x204
STDOUT:   LayoutIFrame {IFRAME} at (0,0) size 204x204 [border: (2px inset #EEEEEE)]
STDERR: [28392:28392:0111/113203.848021:WARNING:render_frame_host_impl.cc(2696)] OnDidStopLoading was called twice.
STDERR: [1:1:0111/113203.889376:FATAL:blink_test_runner.cc(829)] Check failed: 0 != snapshot.info().width() (0 vs. 0)
STDERR: #0 0x000003142dbc base::debug::StackTrace::StackTrace()
STDERR: #1 0x00000316160c logging::LogMessage::~LogMessage()
STDERR: #2 0x000003135ae9 content::BlinkTestRunner::OnPixelsDumpCompleted()
STDERR: #3 0x000006c0a562 test_runner::(anonymous namespace)::CaptureCallback::DidCompositeAndReadback()
STDERR: #4 0x00000314457a base::debug::TaskAnnotator::RunTask()
STDERR: #5 0x0000028060e1 blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue()
STDERR: #6 0x0000028059ce blink::scheduler::TaskQueueManager::DoWork()
STDERR: #7 0x000001608458 _ZN4base8internal7InvokerINS0_9BindStateIMN7content17ResourceScheduler24ScheduledResourceRequestEFvNS3_12_GLOBAL__N_19StartModeEEJNS_7WeakPtrIS5_EES7_EEEFvvEE7RunOnceEPNS0_13BindStateBaseE
STDERR: #8 0x00000314457a base::debug::TaskAnnotator::RunTask()
STDERR: #9 0x00000280bd58 blink::scheduler::internal::ThreadControllerImpl::DoWork()
STDERR: #10 0x000001608458 _ZN4base8internal7InvokerINS0_9BindStateIMN7content17ResourceScheduler24ScheduledResourceRequestEFvNS3_12_GLOBAL__N_19StartModeEEJNS_7WeakPtrIS5_EES7_EEEFvvEE7RunOnceEPNS0_13BindStateBaseE
STDERR: #11 0x00000314457a base::debug::TaskAnnotator::RunTask()
STDERR: #12 0x0000031687d6 base::internal::IncomingTaskQueue::RunTask()
STDERR: #13 0x000003166c47 base::MessageLoop::RunTask()
STDERR: #14 0x000003167064 base::MessageLoop::DeferOrRunPendingTask()
STDERR: #15 0x000003167328 base::MessageLoop::DoWork()
STDERR: #16 0x00000316aea0 base::MessagePumpDefault::Run()
STDERR: #17 0x00000316649c base::MessageLoop::Run()
STDERR: #18 0x00000318f066 base::RunLoop::Run()
STDERR: #19 0x0000066c244b content::RendererMain()
STDERR: #20 0x0000028918f4 content::RunZygote()
STDERR: #21 0x00000289221b content::RunNamedProcessTypeMain()
STDERR: #22 0x000002892d06 content::ContentMainRunnerImpl::Run()
STDERR: #23 0x000004946f24 service_manager::Main()
STDERR: #24 0x000001c4e891 content::ContentMain()
STDERR: #25 0x00000144f152 main
STDERR: #26 0x7f9042d2df45 __libc_start_main
STDERR: #27 0x00000144f02a _start
STDERR: 
STDERR: [28392:28478:0111/113204.100897:WARNING:crash_handler_host_linux.cc(330)] Could not translate tid, attempt = 1 retry ...
 
Cc: creis@chromium.org alex...@chromium.org nasko@chromium.org arthurso...@chromium.org
Components: Internals>Sandbox>SiteIsolation
Labels: OS-Linux
Status: Available (was: Untriaged)
Summary: iframe-script-modify-attr.html fails with site-per-process. Check failed: 0 != snapshot.info().width() (was: blink_test_runner DCHECK failed during dryrun)
I consistently get the same crash with "site-per-process" on the same test.

Command:
python third_party/WebKit/Tools/Scripts/run-webkit-tests -t Debug --additional-driver-flag="--enable-features=site-per-process" http/tests/misc/iframe-script-modify-attr.html

Probably unrelated: I am using a tiled windows manager (i3) (???)

I took a look a the last set of build. It is failing on a few of them. It looks like this test is flaky. I will disable this test soon.
Example:
https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/624124
https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/624100
https://ci.chromium.org/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/624076
...
 Issue 801992  has been merged into this issue.
Labels: Sheriff-Chromium
I'm already landing https://chromium-review.googlesource.com/c/chromium/src/+/866731 , which will mark a few tests as flaky.
Cc: dpranke@chromium.org jbudorick@chromium.org
+dpranke, jbudorick who've been working on enabling site-per-process layout tests lately (e.g. issue 801478).

Marking the tests should at least unblock WPT imports who've been failing since yesterday, so thanks for that!
Project Member

Comment 5 by bugdroid1@chromium.org, Jan 15 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/419c1a6fcb3cf159e7c4c8ec20447fdd29c36230

commit 419c1a6fcb3cf159e7c4c8ec20447fdd29c36230
Author: Morten Stenshorne <mstensho@chromium.org>
Date: Mon Jan 15 12:40:53 2018

Mark some site-per-process layout tests as flaky.

Picked failures from a few bot runs, and threw in a few related ones on
my own, which flake locally.

TBR=pfeldman@chromium.org

Bug:  801338 
Change-Id: Icd35669d2587418a7bffa0c73481d0e34b090544
Reviewed-on: https://chromium-review.googlesource.com/866731
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#529257}
[modify] https://crrev.com/419c1a6fcb3cf159e7c4c8ec20447fdd29c36230/third_party/WebKit/LayoutTests/FlagExpectations/site-per-process

Labels: -Sheriff-Chromium
Mergedinto: 667551
Status: Duplicate (was: Available)

Sign in to add a comment