On 2025-02-26 12:28:29 -0800, Paul Eggert wrote: > On 2/26/25 08:06, Vincent Lefevre wrote: > > Hmm... The upstream bug was closed and archived more than 3 years ago! > > I'm Cc'ing Paul, who closed the bug upstream. > > I assume the upstream bug is <https://bugs.gnu.org/18454>.
Yes (this is written at the top of the web page of the Debian bug). > Can you supply more details, such as PCRE2 version, locale, > hardware, and a test case for this new problem? After some tests, this is actually a different bug since text files are affected too. To reproduce: $ seq 600000000 > file $ ls -l --human-readable file -rw-r--r-- 1 vinc17 vinc17 5.5G 2025-02-26 22:10:29 file $ time grep x file Command exited with non-zero status 1 0.10user 0.48system 0:00.59elapsed 99%CPU (0avgtext+0avgdata 2048maxresident)k 0inputs+0outputs (0major+161minor)pagefaults 0swaps $ time grep -P x file Command exited with non-zero status 1 15.92user 0.47system 0:16.39elapsed 99%CPU (0avgtext+0avgdata 2560maxresident)k 0inputs+0outputs (0major+176minor)pagefaults 0swaps pcre2grep also takes a lot of time, whether -U is given or not. So this new issue may be a bug in the PCRE2 library. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
