Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More informations about the source of user-callback and event-listener scripts #12

Open
rackaam opened this issue Apr 8, 2024 · 1 comment

Comments

@rackaam
Copy link

rackaam commented Apr 8, 2024

We are using the LoAF api to try to pinpoint the origins of some performance issues but most of the time we don't get enough information to have something actionable.

Most of the scripts are "user-callback" or "event-listener":

{
    "name": "script",
    "entryType": "script",
    "startTime": 5038.5999999996275,
    "duration": 767,
    "invoker": "TimerHandler:setTimeout",
    "invokerType": "user-callback",
    "windowAttribution": "self",
    "executionStart": 5038.5999999996275,
    "forcedStyleAndLayoutDuration": 111,
    "pauseDuration": 0,
    "sourceURL": "",
    "sourceFunctionName": "",
    "sourceCharPosition": -1
}
{
    "name": "script",
    "entryType": "script",
    "startTime": 5867.299999998882,
    "duration": 35,
    "invoker": "XMLHttpRequest.onreadystatechange",
    "invokerType": "event-listener",
    "windowAttribution": "self",
    "executionStart": 5867.299999998882,
    "forcedStyleAndLayoutDuration": 0,
    "pauseDuration": 0,
    "sourceURL": "",
    "sourceFunctionName": "",
    "sourceCharPosition": -1
}

Is there any way to get more information such as where the setTimeout has been called?

@mmocny
Copy link

mmocny commented May 28, 2024

Might be related to #11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants