David, thanks. Unfortunately I still saw a 75 Mbyte increase in memory use when running normal mode decode for about an hour. I’ve got the dtruss utility running, but I can’t at the moment see anything of concern. I really need to run this for several hours.
Nigel > On 12 Nov 2018, at 13:00, David Tiller <[email protected]> wrote: > > Nigel, > > I use OS 10.13.6 and WSJTX rc3. I performed the following tests with no audio > (so no decodes - that eliminates the act of decoding from the equation). > > In short, my results (although very speculative) point to the deep decoder as > the culprit. > > Also, there is a system utility available called 'dtruss' that can trace > system calls. That may help you narrow it down, although when I tried it, it > made the UI look odd and act as if it was the first run of the program (the > initial splash screen was displayed, etc). > > fred:MacOS fred$ pwd > /Users/fred/Applications/wsjtx.app/Contents/MacOS > fred:MacOS fred$ sudo dtruss ./wsjtx > > > 1) I ran wsjtx in WSPR mode with 'deep' decode on and saw the memory usage > climb from 147.2M to 157.9M some 7 minutes later. > > <Screen Shot 2018-11-12 at 7.35.25 AM.png> > > > <Screen Shot 2018-11-12 at 7.42.37 AM.png> > > > > 2) I stopped wsjtx and re-ran it with 'normal' decode on. Memory usage start > and 124.2M and _dropped_ to 123.2M after 7 minutes or so. > > <Screen Shot 2018-11-12 at 7.43.09 AM.png> > > > <Screen Shot 2018-11-12 at 7.50.07 AM.png> > > > -- > David Tiller > Sr. Architect/Lead Consultant | CapTech > (804) 304-0638 | [email protected] > <mailto:[email protected]> > > > >> On Nov 12, 2018, at 3:02 AM, Nigel Squibb <[email protected] >> <mailto:[email protected]>> wrote: >> >> I have done some further testing, and whatever is casuing the memory leak it >> isn’t related to the file system. I did a fresh install of OS-X 10.11(El >> Captain), which reformats the >> disk, and the memory leak persisted. Now back on OS 10.13.6- also a clean >> install (This older Mac Mini won’t run 10.14), and WSJT still predictably >> increases in memory usage by about 80 -100 Mbyte per hour, (Activity >> monitor), and then hangs when it gets to about 3 Gbytes. (8 Gbyte memory in >> machine) >> No other non-system software is running (even Activity monitor is closed) in >> normal use, so no web browser etc. >> I have tried turning reporting spots off- no difference. >> I have tried running without audio input (i.e. no decodes) - no difference >> >> I'm only using WSPR mode, so continuous operation is a must, although I >> could obviously use a script to automatically kill and restart once every 24 >> hours or so. >> >> Others here seem not to have this issue, so would greatly appreciate any >> pointers as to further diagnostics I can run to pinpoint what is going on. >> >> Nigel >> >> _______________________________________________ >> wsjt-devel mailing list >> [email protected] <mailto:[email protected]> >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
