tag:support.markedapp.com,2011-09-11:/discussions/problems/147989-memory-leakMarked: Discussion 2018-06-27T21:24:36Ztag:support.markedapp.com,2011-09-11:Comment/455762102018-06-27T20:31:33Z2018-06-27T20:31:34ZMemory Leak<div><p>Hi Brett,</p>
<p>Sorry I can't provide any details, but I thought you might want to know:</p>
<ul>
<li>
<p>I came back to my Mac the other morning, Marked 2 was left up and running overnight. It had been suspended by the system because it was using over 40gb of RAM. Not sure why and I didn't think to take a screenshot before killing the job.</p>
<ul>
<li>Marked 2.5.18 (952)</li>
<li>MacOS Sierra 10.12.6</li>
<li>iMac Retina 27 Late 2015</li>
<li>32gb RAM</li>
</ul>
</li>
</ul>
<p>If it happens again, I'll follow up with more detail.</p>
<p>Thanks,<br>
Anthony</p></div>Anthony Castillotag:support.markedapp.com,2011-09-11:Comment/455762102018-06-27T20:41:05Z2018-06-27T20:41:05ZMemory Leak<div><p>Was Marked watching a folder while running overnight? I've seen some<br>
issues with the folder watcher under High Sierra that I'm currently<br>
trying to track down.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/455762102018-06-27T21:24:35Z2018-06-27T21:24:35ZMemory Leak<div><p>Hi,</p>
<p>Good question. I never realized that opening a folder would also have<br>
the app watch the entire folder for changes. (I thought it just opened<br>
whatever was already in the folder, and then only watched those.)</p>
<p>I'll see if I can try it both ways and then if it happens again. I'll<br>
let you know if I find anything out.</p>
<p>Thank you,<br>
Anthony</p></div>Anthony Castillo