See if this thread helps at all...
https://groups.io/g/N1MMLoggerPlus/topic/89323949
Mike W9MDB
On Wednesday, August 24, 2022 at 04:59:32 PM CDT, Ron WV4P via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
I was able to produce this RTE, again it's N1MM but may hold clues ?
Ron WV4P
N1MMLogger.net - Version 1.0.9635.0
Built: 8/24/2022 10:45:18 AM
Microsoft Windows NT 10.0.19044.0,64:1,en-US,en-US,.NET:528372
Error occurred at: 8/24/2022 4:49:14 PM in Thread: Name: '', Id: '33', Prio:
'Normal'
---------------------------------------------------------------------------------------
System.Net.Sockets.SocketException (0x80004005): An established connection was
aborted by the software in your host machine
at System.Net.Sockets.Socket.BeginReceive(Byte[] buffer, Int32 offset, Int32
size, SocketFlags socketFlags, AsyncCallback callback, Object state)
at N1MMLogger.Net.AsyncTcpListener.ReceiveCallback(IAsyncResult ar) in
C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM
Logger.Net\Classes\AsyncTcpListener.vb:line 142
---------------------------------------------------------------------------------------
Call Stack before the runtime error: at
System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at N1MMLibrary.SharedLib.CallStackString() in
C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM
Library\Classes\SharedCode.vb:line 118
at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName,
String Info, String additionalInfoForLogFile) in
C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM
Logger.Net\Modules\SharedCode.vb:line 223
at N1MMLogger.Net.AsyncTcpListener.ReceiveCallback(IAsyncResult ar) in
C:\Users\nsafr\source\Workspaces\VS2019\N1MM Logger on .NET\main\N1MM
Logger.Net\Classes\AsyncTcpListener.vb:line 162
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr
userToken)
at
System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32
errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32
errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
On Wed, Aug 24, 2022 at 3:22 PM Ron WV4P <wv4...@gmail.com> wrote:
This is the Error that pops up when it first crashes. I presume this is
generated by N1MM when the WSJT window disappears.The Orphaned JT9 process
always prevents restarting WSJT. Killing it in Task Manager Sometimes allows
you to reopen it, sometimes not. Sometimes there is one JT9 process, sometimes
2. Often the Second WSJT window will continue working, killing Both JT9
processes seems to have no effect on it.
I played for a couple hours trying to find a way to Make it fail, I was unable.
For a while it made me think it was not going to fail. Then it did, and even
after a reboot it failed within 10 min afterwards.
Ron, WV4P
Ron, WV4P
On Tue, Aug 23, 2022 at 9:15 PM Joe Taylor via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
Hi Dennis and Ron,
Thanks for your reports. This message is off-list, since your needs are
rather specialized -- but I have CC'd other members of our core
development group.
On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote:
> I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using
> an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2-
> the EW just disappeared from the screen and I got an error box related
> to TCP. Since that first stoppage- or crash- I've had 4 more crashes.
> The longest I've operated since then has been about 40 minutes.
>
> So, the bug that is causing the program to suddenly close, has not been
> found. And it was looking so good!
On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote:
> Same here, running N1MM with 2 instances it keeps crashing and locking
> everything down when it does. It took a long time for the first
> occurrence but now its lucky to stay up 30 min.
...
> I'll be single op.
> If anyone makes it work with the Max Distance feature they will have a
> distinct advantage. Sadly it's back to 2.54 for me, I could not make it work
> reliably. I'll run it again this evening to try and get some screen shots and
> data that might help the Smart people, before I swap back to the stable
> version.
> Good luck, Dennis ! You rocked the last one.
We'll be happy to help you guys to isolate the problem you're having,
apparently with communication between WSJT-X and N1MM+, but I must
caution you that it may take some time. Moreover, in the immediate
future my time is largely committed to a paper on the EME Echo mode
features in WSJT-X 2.6.0.
None of our program versions 2.6.0-rc1, -rc2, or -rc3 have intentional
changes to the way communications take place with an external program
such as N1MM+. At present I don't know the details of what happens when
you say it (I suppose you mean WSJT-X) crashes. Any error message?
What was happening just before the failure? Is WSJT-X doing any rig
control? Can you stress-test the situation in a way that reliably
forces a failure?
These release-candidate versions of WSJT-X 2.6.0 have been bullet-proof
in my own usage patterns, including in the ARRL-DIGI contest back in
June at W2ZQ. But we were using it alone, not with N1MM. Of course,
WSJT-X does not have built-in SO2R features. Are there other reasons
that you want N1MM in addition to WSJT-X for, say, the WW-DIGI contest?
None of us is a regular user of the N1MM + WSJT-X combination, so we
really need your help -- and possibly that of the N1MM development
group, to track down what's flaky about this two-program kludge.
-- 73, Joe, K1JT
_______________________________________________
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
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
