MinimWatch crashes when using Trace

[simbun]

Hi @simoncn,

When debugging issues with control points the MinimServer trace logging comes in really handy, but certain control points request 2,000 items at a time (WiiM) and cause MinimWatch to crash with:
   
It looks like the DIDL is being written out to a single line in the log window, and at some point it can't accept any more.

The MinimServer.log contains what I'm after so it's not the end of the world if it can't be solved, although I did have to stop MinimServer once because every time I reopened the log window it would start filling up with more DIDL and crash.

[simoncn]

Please post the MinimWatch crash log file that was created for this error.

[simbun]

(05-12-2023 12:29)simoncn Wrote:  Please post the MinimWatch crash log file that was created for this error.

I looked for it on the server initially, but have just realised that it would be on the client!

[simoncn]

Thanks for this. I have found the bug that is causing this crash. It will be fixed in the next MinimWatch update.

[simbun]

That's great news!

Thanks Simon.

[simoncn]

The fix for this problem is now available in MinimWatch update 111 and MinimServer update 246.

[simbun]

That's fixed the crash but I think the output has changed, maybe deliberately?

In debug mode I see:

Code:

10:09:28.103 Thread-24:  NumberReturned=2000 TotalMatches=4375 UpdateID=180
...
10:09:28.517 Thread-16:  NumberReturned=2000 TotalMatches=4375 UpdateID=180
...
10:09:28.922 Thread-24:  NumberReturned=375 TotalMatches=4375 UpdateID=180
...

but in trace mode I only see the result of the last request:

Code:

10:10:27.318 Thread-23:  NumberReturned=375 TotalMatches=4375 UpdateID=180
10:10:27.326 Thread-23:  Result=<DIDL-Lite ...

I'm sure that I saw everything before (for requests that didn't crash MinimWatch) but I may be mistaken.

The underlying MinimServer log contains the full trace so I'm wondering if MinimWatch is only showing the last <XX> KB? If it's for performance reasons that's fine, at least the crash is fixed and I can still get it from the log.



On a completely unrelated note, when I open the WiiM control point I receive the following messages in the MinimServer.log file:

Code:

10:26:30.583 Thread-26: ohNet: SSDP Multicast      HttpError (sender=192.168.20.143:50694) from OpenHome/Net/Ssdp.cpp:501.  Received: Host: 239.255.255.250:1900
Mx: 3
Man: "ssdp:discover"

10:26:30.584 Thread-27: ohNet: SSDP Multicast      HttpError (sender=192.168.20.143:50694) from OpenHome/Net/Ssdp.cpp:501.  Received: Host: 239.255.255.250:1900
Mx: 3
Man: "ssdp:discover"

10:26:30.702 Thread-24: ohNet: ReaderError handling  for
10:26:30.710 Thread-23: ohNet: ReaderError handling  for
10:26:32.678 Thread-27: ohNet: SSDP Multicast      HttpError (sender=192.168.20.143:50694) from OpenHome/Net/Ssdp.cpp:501.  Received: Host: 239.255.255.250:1900
Mx: 3
Man: "ssdp:discover"

With the 'SSDP Multicast HttpError' repeating constantly.

Does this mean anything to you?

[simoncn]

The log window can contain up to 500,000 bytes of output data. Running with Trace enabled creates additional output that can cause previous lines to scroll up beyond the top of the window and be permanently lost from view. These lines are still available in the log file. For this reason, it is better not to run MinimServer with Trace enabled unless you really need some information that requires this setting.

This "SSDP Multicast HttpError" message means that the ohNet stack used by MinimServer has received an SSDP message with invalid contents, presumably sent by the WiiM control point.

[simbun]

(12-12-2023 15:23)simoncn Wrote:  The log window can contain up to 500,000 bytes of output data. Running with Trace enabled creates additional output that can cause previous lines to scroll up beyond the top of the window and be permanently lost from view. These lines are still available in the log file.

That's what I thought and is perfectly understandable.

(12-12-2023 15:23)simoncn Wrote:  This "SSDP Multicast HttpError" message means that the ohNet stack used by MinimServer has received an SSDP message with invalid contents, presumably sent by the WiiM control point.

Thanks. I'll log it with WiiM.