View Single Post
Old 04-06-2019, 09:19 AM   #144
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,887
Karma: 6120478
Join Date: Nov 2009
Device: many
So virtually no change from lid closed sleeping overnight. That is what I expected. A process that is actually sleeping and not being constantly awakened should not even experience true memory leaks. And it appears yours did not. From your last screen capture it shows Preview was open. Did you run the test that way?

So lid down sleeping does not appear to affect Sigil. My only worry would be having a system utility run that cleans of flushes files in a temp folder. That bug actually hit Macs that sleep for longer than 3 or 4 days. But the user can work around that by setting their own temp directory.

So it appears that all is well based on that test.

Quote:
Originally Posted by brent63 View Post
Okay I did what you asked except I had my normal setup, so the preview window was open all night (See Attached) with only a 1.5 MB uptick in memory.
(See Attached)

Last edited by KevinH; 04-06-2019 at 09:23 AM.
KevinH is offline   Reply With Quote