https://bugs.kde.org/show_bug.cgi?id=418636
--- Comment #1 from Henry Pfeil <hpf...@psnarf.org> --- There appears to be more regex expressions that induce this runaway memory allocation as the number of matches increases. "Processed 0 of x matches" where x increases beyond the number of lines in the file, eventually increasing beyond the number of characters in the file. This began as my feeble knowledge of regexes tried to match a space followed by, for example, (0x00007ffc8f6a4000), without resorting to sed '/ \(0x[0-9]|[a-f]+\)/d' I thought if I just replaced the " (0x" with a linefeed, I could just sed '/00/d' and be done with it. Then I noticed that searching for "\/usr\/lib64" also invoked the runaway, only slower, so I could stop the search after Kate's memory footprint rose to 2gb. Could there be a loop in Kate's regex code that does not reach an end condition? -- You are receiving this mail because: You are watching all bug changes.
