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

Issue 688185 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 663533
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 3
Type: Bug



Sign in to add a comment

misc issues with frame viewer

Project Member Reported by skobes@chromium.org, Feb 3 2017

Issue description

I tried to use chrome://tracing to examine the layer tree for a simple test page (http://output.jsbin.com/fefilo/quiet).

I've attached a screenshot of the page, and of the tracing window.  Here are some things I observe:

- A yellow banner saying "Some problems were encountered"; clicking "More info" shows "Your trace didn't have pictures for every layer. Old chrome versions had this problem".

- The lower left pane has a list of cc layers with no indication of the tree structure.  I can't tell which layers are siblings, parents, or children of each other.

- GraphicsLayer::debugName() reports a friendly name for each layer like "LayoutBlockFlow (relative positioned) DIV id='box'".  But I can't find these names anywhere in the frame viewer, even in the JSON debug info.

- The 3D rendering of the layer tree looks nothing like what I would expect.  There is a very wide short rect, and a rect that fills most of the window minus some space at the top, but I don't see anything that looks like the #box element or the scrollbars.

- Zooming is very difficult because the image pans out of view very quickly for small zoom increments.  Zooming should preserve the point under the mouse.

- There is a huge amount of whitespace below the image that I have to scroll through to reach the JSON debug info and the picture debugger link.

Let me know if I should file separate bugs for these, or if I'm doing something wrong, or if frame viewer is deprecated or something.
 
page.png
11.8 KB View Download
tracing.png
231 KB View Download
Summary: misc issues with frame viewer (was: frame viewer virtually unusable)

Comment 2 by ajha@chromium.org, Feb 3 2017

Labels: Needs-Milestone
Labels: Needs-Feedback
Unable to reproduce the issue on Linux ubuntu 14.04 ,Windows 7 & Mac 10.12.2 using chrome stable version#56.0.2924.87 & Canary#58.0.3006.0 as per comment#0.
Please find the attached screencast for reference & it would be better if you provide us the clear steps/ screencast to reproduce the issue.
Thanks in advance!!

688185.ogv
5.1 MB View Download
Labels: OS-Mac
Status: Untriaged (was: Unconfirmed)
I encountered the same issue today in Chrome Canary 59.0.3036.0.
Steps to repro: Start Chrome with --enable-skia-benchmarking, check "Frame Viewer" profile, click Record, click on LayerTreeHostImpl snapshots. The frame viewer shows "Some problem were encountered." Saved pictures cannot be seen in the analysis view.


JS Console shows:

Uncaught TypeError: Cannot read property 'forEach' of undefined
    at HTMLElement.set displayItemList [as displayItemList] (chrome://tracing/tracing.js:6443:2774)
    at HTMLElement.updateContents (chrome://tracing/tracing.js:6461:42)
    at HTMLElement.set objectSnapshot [as objectSnapshot] (chrome://tracing/tracing.js:4489:1029)
    at HTMLElement.set modelEvent [as modelEvent] (chrome://tracing/tracing.js:4489:875)
    at HTMLElement.set selection [as selection] (chrome://tracing/tracing.js:4492:361)
    at createSubView (chrome://tracing/tracing.js:4514:107)
    at chrome://tracing/tracing.js:4518:392
    at Map.forEach (native)
    at HTMLElement.onSelectionChanged_ (chrome://tracing/tracing.js:4518:341)
Screen Shot 2017-03-09 at 10.48.23 PM.png
296 KB View Download
Should probably be duped into  issue 663533 . Frame viewer has been broken since 2015 it seems.
Mergedinto: 663533
Status: Duplicate (was: Untriaged)
mac triage: duping per #5.

Sign in to add a comment