You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I quickly used Performance tab in Vivaldi dev tools for the first time and it tells me that almost all of CPU is taken by some /[^<>]+(?=<\/bdi><\/a><\/h2>)/g regular expression:
The VA open edits source code is bigger in size… 🤔
I try zero space positive look behind in addition to my zero space positive look ahead to see if it improves performance: /(?<=<bdi>)[^<>]+(?=<\/bdi><\/a><\/h2>)/
It's acting better in EmEditor but It does not seem to be supported by Vivaldi…
I came up with /<h2><a href="[^"]+"><bdi>([^<]+)<\/bdi><\/a><\/h2>/ the fastest regular expression for what I want in RexExr but it requires some changes in my script to retrieve the grouped value, now that I don't use the zero width positive look ahead no more (which seemed to be the CPU heavy demanding feature).
Mohsen Namjoo is scanned in 1.2ms instead of very long time
Various Artists is scanned in 1.6ms instead of 35.3ms!
I don't understand why it freezes these two particular release pages.
They have the same artist, so it's because of something in the artist open edits.
In fact, any of the pages for Mohsen Namjoo will have this freeze, including simply the artist page itself.
But there are only 64 open edits, which is far less than Various Artists 500+ edits with no freezes on any of my VA releases.
The text was updated successfully, but these errors were encountered: