Comment 1 for bug 165143

This does not mean that it was korgac using the memory, just that it was it's allocation that caused oom-killer to start killing some processes. If this is repeating, you should investigate with top which processes are actually using most of the memory. If you find out that it is korgac using extensive amount of memory, feel free to reopen the bug.