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

Issue 652332 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Event listeners are treated as a blackbox in the timeline

Reported by ri.j...@gmail.com, Oct 3 2016

Issue description

Chrome Version       : 53.0.2785.116 and 55.0.2879.0 canary

What steps will reproduce the problem?
(1) Open timeline and load page with a very slow event listener (e.g. the attached test.html)
(2) Notice that there are no details about what happens during the event listener execution

What is the expected result?

Below "Event (event-name)" should be a row with the functions which have been called during the event listener execution.

What happens instead?

It just shows some garbage collection activity (or nothing at all).

Please provide any additional information below. Attach a screenshot if
possible.

I have attached:
* test.html file to reproduce the problem
* timeline.png which shows that the verySlowFunction() is missing if called in a event handler. At the same time, it is visible if called directly.
* profile.png which shows that the profiler does not have this limitation.

 
timeline.png
117 KB View Download
profiler.png
77.8 KB View Download
test.html
310 bytes View Download
Components: Platform>DevTools
Labels: Needs-Bisect M-53
Owner: alph@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: caseq@chromium.org jmukthavaram@chromium.org pfeldman@chromium.org
Labels: -Type-Bug -Pri-3 -M-53 -Needs-Bisect M-55 OS-Linux OS-Mac OS-Windows Pri-2 Type-Bug-Regression
Able to reproduce the issue in Current Chrome stable (53.0.2785.143), mac,Linux and  canary(55.0.2880.0) - displays "Event(event-name)" with blank function.

Manual Bisect:

Good build:50.0.2633.0
Bad build:50.0.2634.0

Bisect tool info:

CL : https://chromium.googlesource.com/chromium/src/+log/663559bc7a88fbe864a404f80687cf3b8f7a77ed..21a110d3e3c2367300904f9337da966f6f531b59

Possible suspect:

https://codereview.chromium.org/1624783002

Please reassign if this is not related to your change.



 Issue 652333  has been merged into this issue.
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 28 2016

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

commit ce6a35209d7ebeb969d372c0bf23c0c403bdd83d
Author: alph <alph@chromium.org>
Date: Mon Nov 28 21:58:08 2016

DevTools: allow JS frames under EventDispatch

BUG= 652332 

Review-Url: https://codereview.chromium.org/2528553002
Cr-Commit-Position: refs/heads/master@{#434732}

[modify] https://crrev.com/ce6a35209d7ebeb969d372c0bf23c0c403bdd83d/third_party/WebKit/Source/devtools/front_end/timeline_model/TimelineJSProfile.js

Comment 6 by alph@chromium.org, Nov 28 2016

Labels: M-56 Merge-Request-56 Merge-Request-55
Status: Started (was: Assigned)

Comment 7 by gov...@chromium.org, Nov 29 2016

Before we approve merge to M55 branch 2883, could you please make sure this change is well baked/verified in Canary/Dev and safe to merge to M55?

Comment 8 by dimu@chromium.org, Nov 29 2016

Labels: -Merge-Request-55 Merge-Review-55 Hotlist-Merge-Review
[Automated comment] Less than 2 weeks to go before stable on M55, manual review required.

Comment 9 by dimu@chromium.org, Nov 29 2016

Labels: -Merge-Request-56 Merge-Approved-56 Hotlist-Merge-Approved
Your change meets the bar and is auto-approved for M56 (branch: 2924)
Per manual bisect at #3, this issue exists since M50 (50.0.2634.0). We're VERY close to M55 stable promotion and we're only taking critical merges in. Can this wait until M56?

Comment 11 by alph@chromium.org, Nov 30 2016

The fix is pretty safe and there's a request from a customer to fix the issue. So we'd like to merge it into M55 as well.

Comment 12 by alph@chromium.org, Nov 30 2016

It's not urgent for M55. It's ok if it eventually gets into M55 update.
Ok, sounds good. It will miss first stable rollout but we will take it in for future M55 stable update so by then change will be baked in dev too. 
Project Member

Comment 14 by bugdroid1@chromium.org, Nov 30 2016

Labels: -merge-approved-56 merge-merged-2924
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1199c79ab789656089f1b50f98ee4bc13da9a783

commit 1199c79ab789656089f1b50f98ee4bc13da9a783
Author: Alexei Filippov <alph@chromium.org>
Date: Wed Nov 30 21:29:47 2016

DevTools: allow JS frames under EventDispatch

BUG= 652332 

Review-Url: https://codereview.chromium.org/2528553002
Cr-Commit-Position: refs/heads/master@{#434732}
(cherry picked from commit ce6a35209d7ebeb969d372c0bf23c0c403bdd83d)

Review URL: https://codereview.chromium.org/2541043003 .

Cr-Commit-Position: refs/branch-heads/2924@{#209}
Cr-Branched-From: 3a87aecc31cd1ffe751dd72c04e5a96a1fc8108a-refs/heads/master@{#433059}

[modify] https://crrev.com/1199c79ab789656089f1b50f98ee4bc13da9a783/third_party/WebKit/Source/devtools/front_end/timeline_model/TimelineJSProfile.js

Cc: tkonch...@chromium.org
Labels: Needs-Feedback
Tested the same on win10 mac and Linux using chrome version 56.0.2924.14 - Observed veryslow function in "dispatchEvent" as shown in the screenshot.

Event (test) is displayed without any functions

Could you please let us know the expected result to verify the fix
Screen Shot 2016-12-02 at 12.18.21 PM.png
367 KB View Download

Comment 17 by alph@chromium.org, Dec 5 2016

Yes, the result is expected. There are functions shown under the Dispatch Event, e.g. (anonymous).
Labels: -Merge-Review-55 Merge-Approved-55
Approving merge to M55 branch 2883 based on comments #11 and #17 and per chat with alph@ this is a supersafe change. Please merge ASAP. Thank you.
Project Member

Comment 19 by bugdroid1@chromium.org, Dec 5 2016

Labels: -merge-approved-55 merge-merged-2883
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/34ca308256952476dbf2519fbe7d70d40a942142

commit 34ca308256952476dbf2519fbe7d70d40a942142
Author: Alexei Filippov <alph@chromium.org>
Date: Mon Dec 05 21:58:38 2016

DevTools: allow JS frames under EventDispatch

BUG= 652332 

Review-Url: https://codereview.chromium.org/2528553002
Cr-Commit-Position: refs/heads/master@{#434732}
(cherry picked from commit ce6a35209d7ebeb969d372c0bf23c0c403bdd83d)

Review URL: https://codereview.chromium.org/2555563002 .

Cr-Commit-Position: refs/branch-heads/2883@{#711}
Cr-Branched-From: 614d31daee2f61b0180df403a8ad43f20b9f6dd7-refs/heads/master@{#423768}

[modify] https://crrev.com/34ca308256952476dbf2519fbe7d70d40a942142/third_party/WebKit/Source/devtools/front_end/timeline_model/TimelineJSProfile.js

Comment 20 by alph@chromium.org, Dec 5 2016

Labels: -Needs-Feedback
Status: Fixed (was: Started)
Labels: TE-Verified-55.0.2283.85 TE-Verified-M55
Verified this issue on Windows-10, Mac OS 10.12 and Ubuntu 14.04 using chrome latest M55 #55.0.2283.85 by following steps mentioned in the original comment. Observed veryslow function() is displayed in the event listeners timeline as expected. Hence adding TE-Verified label.



Screenshot from 2016-12-07 12:05:24.png
268 KB View Download

Sign in to add a comment