Memory Issue when using Kile

[theufman@…]

I noticed recently that when I use Kile for a while, it consumes a lot of memory. After two hours of typing and compiling, it is not unusual for it to claim over 2GB of memory, and it seems that as a result it takes longer and longer for files to compile, forward and inverse searches to take place, etc.

Are there any recommendations as to how to improve this? I am running OSX 10.6.8 with MacPorts 2.1.3.

[cooljeanius (Eric Gallager)]

This is probably an upstream issue. You should report it to the Kile devs if you haven't already.

[theufman@…]

I reported this to the Kile devs. However, their belief is this is a downstream issue, as they have not seen this issue on any other platform. Here is their response. I'm not sure how to proceed.

​https://bugs.kde.org/show_bug.cgi?id=316346

Michel Ludwig <michel.ludwig@…> changed:

What |Removed |Added

---

Status|UNCONFIRMED |RESOLVED

Resolution|DOWNSTREAM

--- Comment #1 from Michel Ludwig <michel.ludwig@…> --- Sorry, but I think that you have to report this problem to the MacPorts community as I haven't encountered such a memory leak on Linux yet,

--

[NicosPavlov]

From the comments in the kde ticket, it seems to me that the memory load may be coming from the communication between different elements such as Kile and Okular. It is not easy to characterise a problem like this, as it may come from different sources. It may be specific to the installation of Macports, but not necessarily.

[mkae (Marko Käning)]

Cc Me!