GIMP uses more system resources than necessary

[Jeb E.]

I am using GNU Image Manipulation Program version 2.8.14 on Ubuntu 14.10 x64 on
my AMD Phonom II X4 machine packed with 8GB DDR3 RAM and more than the
recommended amount of SWAP-Space found in multiple locations throughout my PC,
and even though I have all this caching space and more plus a powerful
processor, GIMP still eats my computer's system resources alive even while
doing some quick editing and touch-ups, specifically when using the Heal tool -
The window will freeze up and continue what it's doing in the background, but
for that time being, it won't let me do much besides that.

It has now gotten to a point where GIMP uses so many system resources all at
one time where it locks up my (USB 2.0) keyboard for all apps and won't let me
use the keyboard at all until GIMP is done doing what it is doing.

I have even switched to the LowLatency Linux Kernel to help speed up my PC and
keep only needed background tasks while using minimal RAM.

See below for a HardInfo chart I pasted stating my Operating System
information:

-Version-
Kernel : Linux 3.16.0-29-lowlatency (x86_64)
Compiled : #39-Ubuntu SMP PREEMPT Mon Dec 15 22:55:59 UTC 2014
C Library : Unknown
Default C Compiler : GNU C Compiler version 4.9.1 (Ubuntu
4.9.1-16ubuntu6)
Distribution : Ubuntu 14.10
-Current Session-
Computer Name : SDB
User Name : jeb (Jeb Eldridge)
Home Directory : /home/jeb
Desktop Environment : Unity (ubuntu)
-Misc-
Uptime : 1 day, 16 hours and 52 minutes
Load Average : 0.29, 0.44, 0.76

Attached is also a screenshot with "About This Computer" info shown.

[Jeb E. (jebeld17)]

Attached here is a full HardInfo Report on my PC, containing all hardware and kernel specs.

[jebeld17 (jebeld17-linux-kernel-bugs)]

Created attachment 163471
About This Computer

I am using GNU Image Manipulation Program version 2.8.14 on Ubuntu 14.10 x64 on
my AMD Phonom II X4 machine packed with 8GB DDR3 RAM and more than the
recommended amount of SWAP-Space found in multiple locations throughout my PC,
and even though I have all this caching space and more plus a powerful
processor, GIMP still eats my computer's system resources alive even while
doing some quick editing and touch-ups, specifically when using the Heal tool -
The window will freeze up and continue what it's doing in the background, but
for that time being, it won't let me do much besides that.

It has now gotten to a point where GIMP uses so many system resources all at
one time where it locks up my (USB 2.0) keyboard for all apps and won't let me
use the keyboard at all until GIMP is done doing what it is doing.

I have even switched to the LowLatency Linux Kernel to help speed up my PC and
keep only needed background tasks while using minimal RAM.

See below for a HardInfo chart I pasted stating my Operating System
information:

-Version-
Kernel : Linux 3.16.0-29-lowlatency (x86_64)
Compiled : #39-Ubuntu SMP PREEMPT Mon Dec 15 22:55:59 UTC 2014
C Library : Unknown
Default C Compiler : GNU C Compiler version 4.9.1 (Ubuntu
4.9.1-16ubuntu6)
Distribution : Ubuntu 14.10
-Current Session-
Computer Name : SDB
User Name : jeb (Jeb Eldridge)
Home Directory : /home/jeb
Desktop Environment : Unity (ubuntu)
-Misc-
Uptime : 1 day, 16 hours and 52 minutes
Load Average : 0.29, 0.44, 0.76

Attached is also a screenshot with "About This Computer" info shown.

[jebeld17 (jebeld17-linux-kernel-bugs)]

Created attachment 163481
HARDINFO REPORT

HardInfo report on my PC

[Jeb E. (jebeld17)]

System monitor status during a simple touch-up using "Heal" in GIMP. This is
the exact same file I was editing from yesterday with the same apps open at the
same time, ceteris paribus.
I could not perform a screenshot while GIMP was incoherent in the background,
forcing me to grab my phone to snap this picture.

As you can see, CPU usage goes through the roof in all four cores and
fluctuates quickly between using 100% of per-core power to much less, almost
like each core is taking a break or trying to push power elsewhere. RAM usage
actually appeared to be pretty stable though, so maybe this was not a RAM issue
too much at all?

The picture was too large to attach... Here is the link to it on Flickr:
https://www.flickr.com/photos/64718148@N06/16099603370/