SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL MultiTerm
SDL Passolo
SDL Speech to Text
SDL Managed Translation - Enterprise
SDL MultiTrans
SDL TMS
SDL WorldServer
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL XPP
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Language Developers
Tridion Developers
Tridion Docs Developers
Xopus Developers
Community Help
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Style Guides
Language Technology Partner Group
SDL Academic Partners
SDL Approved Trainers
SDL Enterprise Technology Partners
XyUser Group
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
Whereas \w+,\s(\w+) is processed without problem, the "complex" \w+,\s(\w+\s\d{1,2}) could not processed within an acceptable time.
Display Filter had no problem with the "complex regex", but cannot be used in my case because I need to make a replacement.
The "solution" was to replace \w with [a-z] (case-insensitive). Even [a-z0-9]+,\s([a-z0-9]+\s\d{1,2}) brought Find to its "knees".
This behaviour concerns Studio 2019.
The regex
\w+,\s(\w+\s\d{1,2})
found the text a, aaa 12
after a gap of ~300 segments instantaneously in my Trados Studio 2019.
Is it a number of segments big enough to notice the lag?
Strange. My document has 3000 segments; the first match at segment 153 took 55 seconds (starting at the first segment)! Even the search starting at segment 135 (3 lines) took 20 seconds, although starting at segment 136 (1 line, as were all intervening segments) was instantaneous.
Whether there is something special in segment 135 or a healthy restart will solve the problem.
I checked the same regex in Notepad++ and it took a noticeable time, but certainly much less than a second, to process 1.7 million chars. I've used some complex regexes taking many seconds to complete, but there is nothing special with yours.
Restart brought no improvement. Display Filter returns instantaneous results.
It picks my curiosity…
If you create a simplified version of your document that fails in the regex Find, please post it and I'll test it.