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

[Bug]: Poor Trace Viewer performance #34035

Open
agg23 opened this issue Dec 16, 2024 · 0 comments
Open

[Bug]: Poor Trace Viewer performance #34035

agg23 opened this issue Dec 16, 2024 · 0 comments
Assignees
Labels
open-to-a-pull-request The feature request looks good, we are open to reviewing a PR

Comments

@agg23
Copy link
Contributor

agg23 commented Dec 16, 2024

Version

1.49.1

Steps to reproduce

  1. Open Trace Viewer on a slower computer
  2. Interact with it and notice the delay manipulating the UI

This can particularly be seen if there's a large number of items in the network log and you expand the details of an item.

Expected behavior

Trace Viewer should be performant and snappy.

Actual behavior

It is not performant and snappy.

Additional context

No response

Environment

System:
    OS: Windows 11 10.0.26100
    CPU: (6) x64 Intel(R) Core(TM) i5-9500 CPU @ 3.00GHz
    Memory: 2.76 GB / 15.81 GB
  Binaries:
    Node: 20.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
  IDEs:
    VSCode: 1.95.2 - C:\Users\agastineau\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
@agg23 agg23 self-assigned this Dec 16, 2024
@agg23 agg23 added the open-to-a-pull-request The feature request looks good, we are open to reviewing a PR label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-to-a-pull-request The feature request looks good, we are open to reviewing a PR
Projects
None yet
Development

No branches or pull requests

1 participant