The issue comes from commit 312778c, the one regarding "Display replace string in EntryListPane". When I revert only that commit, I can work normally with OmegaT, when I include it, Main stays around 100% CPU use after I start a search.
Thank you for the quick fix. I confirm everything works without distressing the CPU (including the regex grouping replace feature which I could not get to work with the previous build)...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This was introduced by [feature-requests:#953]. Thank you for identifying the problematic commit. It is fixed in trunk, r10282.
Related
Feature Requests:
#953Thank you for the quick fix. I confirm everything works without distressing the CPU (including the regex grouping replace feature which I could not get to work with the previous build)...
Fixed in the released version 4.1.4 of OmegaT.
Didier