The problem (decoding stops) recurred last night. The waterfall display continues to work and show multiple signals.
While in this state, the main window decode button remains highlighted and jt9.exe remains at 0% CPU even at the end of each message cycle. Restarting wsjt-x immediately resolves the problem. From this, I conclude that the system clock is sufficiently accurate so that can be ruled out as the source of the promlem. Thanks, Alan / NX1W > On Aug 28, 2019, at 1:46 PM, [email protected] wrote: > > Tom & Bill: > > Thank you for your response. I certainly do *not* expect my reported problem > to be given priority treatment. WSJT-X is a great piece of software and I > appreciate that it requires a lot of work, done by volunteers, to improve and > maintain it. > > The issue I was trying to raise is one of process. The documentation says to > report bugs to the reflector. What happens to emailed bug reports? Can I > search open issues to see if others have seen a similar issue and what > additional information the developers would like? Can I update the bug when > I have more information to add? How can I even know if the developer who > knows that part of the system read the description of my issue? Are all open > issues triaged periodically? Unless someone responds, it’s an information > black hole which can be frustrating for people who report bugs. > > Having done engineering for more than 40 years, I know how difficult it can > be to debug intermittent problems. That’s why I offered to collect data to > help isolate the problem. In your responses, you have given me some things > to look for when the problem recurs. Thank you. > > More people might be willing to get involved in fixing bugs if we could see > the open issues. > > Thanks, > > Alan / NX1W > >> On Aug 28, 2019, at 11:49 AM, Tom Melvin <[email protected] >> <mailto:[email protected]>> wrote: >> >> Alan >> >> Just an observation - for many many people the software works well, the fact >> you cannot reproduce the issue does suggest IF it is an actual wsjtx bug it >> is pretty obscure. >> >> From doing software development in a different life these are the worst sort >> of issues - it could be rig setup, it could be other applications on the PC, >> could be latest windows (or whatever) update, supplier codex, etc. etc. - >> how much time is justified in tracking it down - you said it is a small team. >> >> One option is to log the details, and then see how any others have issues >> over time, if more and more appear - is it same Rig? is it same version of >> the OS, is it the 32 or 64 bit version of the software (there are known >> issues with the 64 bit that are tied to some dev libs) - you never actually >> mentioned which version you were using - if 64 have you tried the 32 bit? >> >> While it may appear dev team are doing nothing it could be they are waiting >> to see if some common factor pops up - 1 week, 1 month, 1 year … Your email >> seems to suggest you sort of expect the team to give it a higher priority >> (may be wrong but that was way I read the mail) >> >> As to a bug list - yes there are a couple of issues I would like to see >> fixed - I know if a list was published there would be a flurry of activity >> (myself included) ‘debating’ the severity/fix time scale - almost everyone >> would want their perceived bug higher up the list. All the dev team would >> end up doing is justifying the details. I can see why no list is publicly >> available. >> >> I’m sure when it can be reproduced it will be fixed. >> >> Collect info, what is happening around the time of the freeze, are .wav >> files saved, anything running on PC at the time, time of day - how random is >> random, daily, weekly - collecting info in a little text file may provide >> pointers you can report to the team that may help. >> >> Regards >> >> Tom >> >> -- >> 73’s >> >> Tom >> GM8MJV (IO85) >> >> >> >> >> >> On 28 Aug 2019, at 15:48, [email protected] >> <mailto:[email protected]> wrote: >> >>> I assume that the development team uses some bug tracking package. Is this >>> correct? >>> >>> If so, was there a defect logged for the issue that I reported here? If >>> so, what is the assigned severity and expected fix release? If not, why >>> not? >>> >>> I, and many others, really appreciate the volunteer work done by the >>> development team on WSJT-X, but it would be really nice for users who >>> report a problem to know the status of their issue… >>> >>> Thanks, >>> >>> Alan / NX1W >>> >>>> On Aug 26, 2019, at 4:02 PM, [email protected] >>>> <mailto:[email protected]> wrote: >>>> >>>> Radio is an IC-7000. >>>> Audio is via USB audio dongle to radio ACC socket. >>>> >>>> 73 >>>> >>>>> On Aug 26, 2019, at 3:04 PM, Bill Somerville <[email protected] >>>>> <mailto:[email protected]>> wrote: >>>>> >>>>> On 26/08/2019 19:19, Alan Kirby wrote: >>>>>> I have a PC continuously running WSJT-X FT8. Once or twice each week, >>>>>> it stops decoding all messages. The clock is accurate to within 100ms >>>>>> and the waterfall shows many signals. >>>>>> >>>>>> Restarting the program immediately fixes the problem.. I have observed >>>>>> this issue with earlier versions of WSJT-X but had hoped the new version >>>>>> would have fixed it. >>>>>> >>>>>> I cannot reproduce this at will – it appears to happen randomly. I >>>>>> would be happy to help the dev team collect data to diagnose this. >>>>>> >>>>>> Windows 10 (64 bit), Intel i5-6400, 2.7GHz 8GB DRAM >>>>>> WSJT-X v2.1.0 >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Alan (NX1W) >>>>> Hi Alan, >>>>> >>>>> which rig and how is it connected to your PC for audio? >>>>> >>>>> 73 >>>>> Bill >>>>> G4WJS. >>>>> >>>>> _______________________________________________ >>>>> wsjt-devel mailing list >>>>> [email protected] <mailto:[email protected]> >>>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7Cc9b2173181844d73251c08d72a588c50%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637024432130899006&sdata=0jj5QtA%2Bna8d33AtgV4fg3ZED6Vc2XKH7Qu9xyHVysU%3D&reserved=0 >>>>> >>>>> <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7C37b5792995b74896f84d08d72bd32b89%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637026058302247126&sdata=EpJMoKz4%2F%2FRCCQDr42MdjZo4VSNM3ZZaiMXsDgvhEUo%3D&reserved=0> >>>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> [email protected] <mailto:[email protected]> >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >> >> _______________________________________________ >> wsjt-devel mailing list >> [email protected] <mailto:[email protected]> >> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7C37b5792995b74896f84d08d72bd32b89%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637026058302267147&sdata=NIAbOUtBTpsnuErcwM3Hzu%2BMKAWPsSY63yvSKGXJ4og%3D&reserved=0 >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
