Home → Problems (v2) →

Memory Leak - 2.1

• Edit

Luca Ferrero

21 Feb, 2013 09:20 PM

Hello, MMC version 2.1 has a memory leak on my macbook air 10.8.2
shortly after launch, it starts using more and more virtual memory without releasing it - creating swap files that take up all of my hard drive free space. It releases the memory and space only by quitting it. Please let me know if you need any log files (and instructions where to find them). Thanks.

1. Support Staff 1 Posted by Fletcher on 22 Feb, 2013 04:05 PM

   

   Luca,

   Thanks for writing.

   Yes, I discovered this as well. The memory leaks are technically in the actual MultiMarkdown code, not the application itself. This means that you will notice memory leaks more when the live preview function is turned on.

   I am working on a fix for this, but it is probably going to mean re-writing the entire open source MultiMarkdown project. So, unfortunately, it can't be fixed overnight.

   I am doing some testing and found a few ways to at least plug some of the larger holes and will include that in the next build.

   • Edit

2. 2 Posted by Luca Ferrero on 22 Feb, 2013 04:13 PM

   

   Thanks for the quick reply. I have turned the preview off, let's see how much it improves for the time being.

   • Edit

3. Support Staff 3 Posted by Fletcher on 22 Feb, 2013 04:19 PM

   

   And I know it's not an ideal solution, but simply quitting and relaunching the app will allow the OS to clean up any leaked memory as well.

   It's at least a band-aid while waiting on a solution.

   • Edit

4. 4 Posted by Matt on 06 Apr, 2013 04:56 PM

   

   Are there any updates on the memory leak situation and a new release that will resolve the issue?

   • Edit

5. Support Staff 5 Posted by Fletcher on 06 Apr, 2013 06:29 PM

   

   Still working on it. As mentioned, it's going to involve rewriting basically all of MultiMarkdown, which will take some time.

   F-

   • Edit

6. 6 Posted by stefano.gor on 11 Apr, 2013 10:04 AM

   

   Unfortunately I've seen this morning ... it's a really amazing problem.

   And ok, I can understand the points reading "Why does Composer use so much memory after it's been open for a while?".
   I understand, but I'm rather saddened.

   • Edit

7. Fletcher closed this discussion on 23 Apr, 2013 01:51 PM.