Can we find which script or function is taking longer than 50 ms?

[Vasikaran]

Can we find which script or function is taking longer than 50 ms?

[spanicker]

We are just starting to work on this, so hopefully in a couple of milestones.

[npm1]

We currently do not plan to expose the script URL, AFAIK. We don't have any concrete future work on how to make attribution better in general. This was deprioritized because of an effort on the sampling profiler, see https://github.com/WICG/js-self-profiling. Ideally after that is shipped then we can use it to surface some longtask attribution.

[vigneshshanmugam]

We did some experiments at Elastic, here are the relevant details - WICG/js-self-profiling#21

[spanicker]

Yes, long tasks V2 will have scriptUrl.
Details in this doc:
https://docs.google.com/document/d/125d69JAC7nyx-Ob0a9Z31d1uHUGu4myYQ3os9EnGfdU/edit

[Vasikaran]

When will you release Long Task V2?

[Vasikaran]

If you release the feature within two or three weeks, it will be very helpful to me.

[RaoufHammami]

Actually , i have the same question as @Vasikaran :
can we find which scripts are culprit for long Tasks (through the name field) and when the V2 of the API will be released.
Thanks

[yoavweiss]

FWIW, I'm cautiously hopeful to make progress on that using Task Tracking as infrastructure on top of which attribution can be built.

[noamr]

Marking as duplicate of #89