Hi, I've tested cooledit 3.11.6-5 (stable, the one that the bug was reported on) and 3.17.1-2 (unstable/testing) and I haven't been able to reproduce the problem you reported here:
http://bugs.debian.org/70630 Does it have to be run in a certain mode, or perform a certain operation before the CPU hogging starts? Any help that you can provide so that I can reproduce (and hopefully fix) this problem will be greatly appresiated. Thanks, David
