starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Performance problems when using quicksearch on chromium based browsers #5722

New Issue
Closed
opened 2025-12-29 19:31:54 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:31:54 +01:00
Owner
Copy Link

Originally created by @promasu on GitHub (Dec 3, 2021).

NetBox version

v3.0.11

Python version

3.7

Steps to Reproduce

  1. Open Devices Page
  2. Type something into the quicksearch field
  3. Browser freezes

We can reproduce this behavior on Chrome 96.0.4664.45 and Edge 96.0.1054.41 with a Netbox with about 340 devices

Expected Behavior

Browser does not freeze

Observed Behavior

Browser freezes

Originally created by @promasu on GitHub (Dec 3, 2021). ### NetBox version v3.0.11 ### Python version 3.7 ### Steps to Reproduce 1. Open Devices Page 2. Type something into the quicksearch field 3. Browser freezes We can reproduce this behavior on Chrome 96.0.4664.45 and Edge 96.0.1054.41 with a Netbox with about 340 devices ### Expected Behavior Browser does not freeze ### Observed Behavior Browser freezes
adam added the type: bug label 2025-12-29 19:31:54 +01:00
adam closed this issue 2025-12-29 19:31:54 +01:00
adam commented 2025-12-29 19:31:55 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Dec 3, 2021):

Duplicate (#7932) and fixed #7933 - will be included in the next release.

@kkthxbye-code commented on GitHub (Dec 3, 2021): Duplicate (#7932) and fixed #7933 - will be included in the next release.
adam commented 2025-12-29 19:31:55 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 3, 2021):

Duplicate of #7932

@DanSheps commented on GitHub (Dec 3, 2021): Duplicate of #7932
adam commented 2025-12-29 19:31:56 +01:00
Author
Owner
Copy Link

@promasu commented on GitHub (Dec 9, 2021):

Hi there,

after i upgraded to 3.1.0 the problem still persists.
In chromium based browsers I get the message

[Violation]'setTimeout' handler took 1642ms - netbox.js:4
[Violation]Forced reflow while executing JavaScript took 1609ms

in the browser console. Using Firefox I don't get any of those messages.

Can you please take another look at this issue?

Kind regards,
Adrian

@promasu commented on GitHub (Dec 9, 2021): Hi there, after i upgraded to 3.1.0 the problem still persists. In chromium based browsers I get the message ``` [Violation]'setTimeout' handler took 1642ms - netbox.js:4 [Violation]Forced reflow while executing JavaScript took 1609ms ``` in the browser console. Using Firefox I don't get any of those messages. Can you please take another look at this issue? Kind regards, Adrian
adam commented 2025-12-29 19:31:56 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Dec 9, 2021):

@promasu - Could you provide specific steps to replicate it? I can't replicate it both locally and on the demo instance? Are you sure your instance is updated properly, and that you have cleared your browser cache?

I tried on the demo instance as well, adding over 1000 devices and filtering on the device page, and it finishes fast (300 ms).

https://demo.netbox.dev/dcim/devices/

image

@kkthxbye-code commented on GitHub (Dec 9, 2021): @promasu - Could you provide specific steps to replicate it? I can't replicate it both locally and on the demo instance? Are you sure your instance is updated properly, and that you have cleared your browser cache? I tried on the demo instance as well, adding over 1000 devices and filtering on the device page, and it finishes fast (300 ms). https://demo.netbox.dev/dcim/devices/ ![image](https://user-images.githubusercontent.com/400797/145386153-3cbf36ef-c757-40b7-8291-f2e3f48fc438.png)
adam commented 2025-12-29 19:31:56 +01:00
Author
Owner
Copy Link

@promasu commented on GitHub (Dec 9, 2021):

Problem solved. I hardcoded the version in the webserver settings. Sorry for bothering you

@promasu commented on GitHub (Dec 9, 2021): Problem solved. I hardcoded the version in the webserver settings. Sorry for bothering you
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5722
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?