You should be able to check the memory usage via Task Manager to determine whether or not it is a memory leak...
-- Thanks, Bill > On July 3, 2019 at 2:52 PM Hasan al-Basri <hbasri.schie...@gmail.com> wrote: > > > I"m baffled, like I said, it acts like a memory leak and I don't think > it's a coincidence that it showed up the very first time after installing and > running RC7 64 bit. > > > 73, N0AN > Hasan > > > On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel < > wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net > > wrote: > > > > Failing audio or rig connections are most always due to > RFI or USB ports going to sleep. > > If RFI low power transmissions can be tested and if they work but > > high power does not then it's RFI. > > The USB ports going to sleep can be solved. > > > > https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices > > > > de Mike W9MDB > > > > > > > > > > On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com > > mailto:rjai...@gmail.com < rjai...@gmail.com mailto:rjai...@gmail.com > > > wrote: > > > > > > I’ve seen this with other radios. Definitely not a flex only issue. > > > > Ria > > N2RJ > > > > On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel < > > wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net > > > wrote: > > > > > > > > > > Peter, > > > > > > Flex has its own set of unique problems and fixes. Suggest > > > you post your question on the Flex forum page. Good luck. > > > > > > Danny > > > AH6FX/W4 > > > > > > On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam < > > > pe...@ni6e.com mailto:pe...@ni6e.com > wrote: > > > > > > > > > Greetings, > > > > > > I have been using WSJT-X quite successfully for several years > > > during > > > June VHF Contests. I experienced a failure of the WSJT > > > program to accept > > > received audio input after several hours of proper operation > > > during the > > > recent Field Day exercise. > > > > > > I'll provide a brief outline and reply with more detail, > > > should it be > > > needed. > > > > > > My computer is a Dell Optiplex 780 running Win 7 Pro SP1, > > > 64-bit. The > > > WSJT-X software version is 2.0.1 7ddcb7. > > > > > > My receiver is a Flex 6500. It passes data to a Flex-supplied > > > "DAX" > > > program that interfaces various applications that wish to > > > receive the > > > audio stream. WSJT accepts the stream and displays results on > > > the Wide > > > Graph and a small audio signal-strength window. Activity > > > proceeded > > > normally for the first three hours of Field Day, until both > > > the Wide > > > Graph and the audio signal-strength stopped showing any > > > incoming audio. > > > > > > I can't offer any help on what might have caused the problem. > > > It was > > > abrupt and seemingly unrelated to any other system actions. I > > > am unable > > > to reproduce the problem. > > > > > > Several operators spent several hours speculating about what > > > a solution > > > might be. Program restarts and computer re-boots (time-tested > > > favorite > > > of generations) changed nothing. The only useful clue was > > > that the DAX > > > audio output stream was present and could be re-directed to > > > Fldigi, but > > > not to WSJT-X. > > > > > > I was able to restore operation for a brief period by > > > stopping WSJT, > > > renaming WSJT.ini and restarting WSJT. That fix lasted for a > > > half hour. > > > Repeating the procedure provided operation for the rest of > > > Field Day. > > > > > > The two .ini files that were renamed are available for your > > > inspection, > > > along with the one that continued to function. > > > > > > Any suggestions you can offer to prevent a recurrence would > > > be greatly > > > appreciated. > > > > > > Regards, > > > Peter > > > NI6E > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > wsjt-devel mailing list > > > wsjt-devel@lists.sourceforge.net > > > mailto:wsjt-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > _______________________________________________ > > > wsjt-devel mailing list > > > wsjt-devel@lists.sourceforge.net > > > mailto:wsjt-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > > > > > _______________________________________________ > > wsjt-devel mailing list > > wsjt-devel@lists.sourceforge.net > > mailto:wsjt-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > _______________________________________________ > > wsjt-devel mailing list > > wsjt-devel@lists.sourceforge.net > > mailto:wsjt-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
