| G’day Shane
Define "a while”.
Wish I could. As my clients keep USA time, and won’t answer any questions until at least 1am Oz time (but more like 7am Oz), I’ll hazard a guess and say about 12 hours running from what they’ve said so far.
I have a devil of a job getting them to accurately report problems. Their IT head hates Macs, and the art room Mac operator who’s my main contact knows ‘zilch’ about them. Real bummer for me.
Sorry I can’t be more specific.
I’m thinking I could include a settable ‘hours’ counter in Mail Managers Setup Page, so MM could be altered to Quit/Restart after the set hours, but it would be FAR more convenient to be able to monitor the MM App memory overhead, and re-start MM on, say, 200MB used.
Can’t find anything on the net though, along the lines of checking RAM usage per App.
Googling seems to indicate, from very old posts, that calling loops can add memory overhead. Can’t find anything recent on memory leakage tho.
my performSelector:"runningLoop:" withObject:(missing value) afterDelay:mailManagerDelay end runningLoopInitializer
on runningLoop:{} my fordEvent()
End of 'runningLoop’ loops back to 'runningLoopInitializer’.
I’ve asked them for a screen shot of the ‘memory’ section of Activity Monitor, sorted by ‘Memory’.
I’ll now add ‘How long does it take’?
Regards
Santa
On 29 Jul 2016, at 1:53 PM, Shane Stanley < email@hidden> wrote: On 29 Jul 2016, at 1:25 PM, Brian Christmas < email@hidden> wrote:
After a while, it starts running slow.
Define "a while".
And what, you ask, was the beginning of it all? And it is this...... Existence that multiplied itself For sheer delight of being And plunged with numberless trillions of forms So that it might find itself innumerably
Sri Aurobindo
|