Issue metadata
Sign in to add a comment
|
Performance tool does not render the flame chart at all when site is using webGL
Reported by
m...@goodboydigital.com,
Sep 28
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Load https://pixijs.io/examples/#/basics/basic.js 2. Open dev tools and Run the performance profiler. 3. Observe the results. What is the expected behavior? flame chart should be rendered correctly when debugging webGL applications What went wrong? flame chart is not being rendered. (attached screen shot) Did this work before? Yes unsure Im afraid, chrome auto updated. Chrome version: 69.0.3497.100 Channel: stable OS Version: OS X 10.13.5 Flash Version:
,
Sep 29
Cannot reproduce. Can you please help us debug the issue. Open DevTools on DevTools (by pressing Ctrl+Shift+I in undocked DevTools) and check if there are any error messages in the console. Also can you please save the profile and attach it to the bug report. Thank you
,
Sep 29
Absolutely, Attached is the screen shot of the dev tools on dev tools. Looks ok? I also attached the profile. This has 100% reproduction rate for me (tried on a few different webGL based sites) Not sure if it makes a difference, I have these two plugins installed (though not active): https://spector.babylonjs.com/ https://benvanik.github.io/WebGL-Inspector/ I heard about this issue from a member of the pixi.js community, I will see if I can get any additional information for you from there. Thanks for looking into this! If you need anything let me know.
,
Sep 29
Same here, although doesn't seem to be consistent. More times than not it doesn't display the flame chart. Chrome 69.0.3497.100, macOS 10.13.6 Seems to work as expected on Canary
,
Sep 29
No errors on DevTools for DevTools. The canvas for the performance timeline is there and correctly sized, but doesn't show. I've also tried running without extensions.
,
Sep 29
I noticed the same thing occurring across multiple computers.
,
Sep 30
Needs-Feedback: on my side chromium: "69.0.3497.81" work chrome: "69.0.3497.100 (Build officiel) (64 bits)" not worked so maybe it between update .81 and .100
,
Oct 2
Here's the list of commits into Chrome between versions: https://chromium.googlesource.com/chromium/src/+log/69.0.3497.81..69.0.3497.100?pretty=fuller&n=10000 V8: https://chromium.googlesource.com/v8/v8/+log/6.9.427.19..6.9.427.23?pretty=fuller&n=10000 No changes to skia.
,
Oct 3
ok i just test last chromium version from nwjs. Chromium: 70.0.3538.22 and it work. I don't know if you have very big difference with chromium and chrome for the debug tool. i can not test chromium "69.0.3497.100" ! sorry
,
Oct 3
,
Oct 3
my test for can not be conclusive because i'm not loading my project debugging webGL applications. it just a fast test sorry. If i update my project to Chromium: 70.0.3538.22, i will share, maybe next month.
,
Dec 11
No new failure reports since M70. Mark as non-repro. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by caseq@chromium.org
, Sep 29Labels: -Pri-2 Pri-1
Owner: alph@chromium.org
Status: Assigned (was: Unconfirmed)