Page crashes when adding host 1f5245c1-e426-5181-9d6d-e4a1b80150a6.

[ptheofan]

Describe the bug
Adding a host that uses a UUID v5 for subdomain crashes the page (js).

Nginx Proxy Manager Version
v2.9.12

To Reproduce
Steps to reproduce the behavior:

1. Go to proxy hosts (/nginx/proxy) and click to add a new proxy host
2. In the domain names paste the following 1f5245c1-e426-5181-9d6d-e4a1b80150a6 and type .. The page crashes (javascript gets stuck to infinite loop and eventually chrome asks to kill the page). 1f5245c1-e426-5181-9d6d-e4a1b80150a6 is a UUID v5 for whatever.example.com (can easily generate more for experimentation from https://www.uuidtools.com/v5). My idea was to put some UUIDv5 as subdomain.

Expected behavior
Continue typing and hit enter to turn it into an entry (tag)

Screenshots

Operating System
Unraid

Additional context
The problem appears to be with selectize. However, because the page crashes it makes it impossible to add the entry.

Workaround: type somewhere the complete host and copy-paste (example, copy-paste the following1f5245c1-e426-5181-9d6d-e4a1b80150a6.example.com will not crash the js)

[FreshImmuc]

didnt crash my dashboard, may be on your end

[chaptergy]

This is due to the nested quantifiers in the regex pattern used to match the strings for selectize. More specifically this seems to be catastrophic backtracing. We would have to use a different regex pattern.

[github-actions]

Issue is now considered stale. If you want to keep it open, please comment 👍

[umutguler]

Can confirm it happens when nesting a lot. While nesting too much may look ugly/impractical. It has its use cases & shouldn't cause the page to crash!

[TheFatPanda97]

are there any follow up to this issue? in the current release of npm I am still getting the same issue where if the subdomain is nested more than 3 levels it freezes the entire frontend