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 Report] UI performance slows after tagging many scenes #4645

Open
bdbenim opened this issue Mar 2, 2024 · 0 comments
Open

[Bug Report] UI performance slows after tagging many scenes #4645

bdbenim opened this issue Mar 2, 2024 · 0 comments
Labels
bug report Bug reports that are not yet verified

Comments

@bdbenim
Copy link
Contributor

bdbenim commented Mar 2, 2024

Describe the bug
During a long session of adding tags to scenes, I'll eventually notice a steep drop-off in performance whenever the tag field is focused, to the point of response times >1s when typing a single character to search for a tag. When this happens, a page refresh seems to resolve the issue immediately.

To Reproduce
Steps to reproduce the behavior:

  1. Go to a page with a tag input, such as a scene, gallery, image, or performer
  2. Enter some tags
  3. Using the same browser tab, and without refreshing at any point, keep repeating steps 1 and 2
  4. Performance will eventually deteriorate significantly

Expected behavior
Performance should remain consistent as long as the load is consistent.

Stash Version: v0.24.3

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Chrome
  • Version: 121.0.6167.189

Additional context
Performance is not noticeably affected on the server side, nor in other aspects of the UI. For instance, I can edit other aspects of a scene just fine but then have the UI struggle once I click in the tag field.

It seems like a resource leak on the client side, but I haven't noticed my browser using significantly more resources when this happens. I tend to have many tabs open across multiple browser windows though, so it might be hard to notice a single tab consuming additional RAM or CPU.

@bdbenim bdbenim added the bug report Bug reports that are not yet verified label Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Bug reports that are not yet verified
Projects
Status: To triage
Development

No branches or pull requests

1 participant