MinimWatch fails on Windows 10 Pro

[simbun]

I've finally moved to Windows 10 and I'm trying to get MinimWatch installed so I can control MinimServer on my Pi.
I've reinstalled Java and MinimWatch a number of times, and MinimServer on Windows 10 loads fine although I can't see it from BubbleUPnP.

$ java -version
java version "1.8.0_241"
Java™ SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot™ 64-Bit Server VM (build 25.241-b07, mixed mode)

Windows: Windows 10 Pro 1909

I've turned the firewall and SRP offf just to make sure I haven't got anything blocking it and I can open the Pi's status page using http://192.168.20.10:9790/
In Windows 10 my network is classified as a 'Private Network' with network discovery turned on.

When running MinimWatch, it flashes up in the taskbar but when I hover over it it disappears.

minimwatch.log

Code:

MinimWatch 0.8.5.3 update 64, Copyright (c) 2012-2019 Simon Nash. All rights reserved.
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode)
Platform default charset is windows-1252
Active subnet is 192.168.20.0

startup.log is empty

When running it from the command line, I see:

Code:

C:\Users\Simon\AppData\Roaming\MinimWatch\bin>startc.cmd
MinimWatch 0.8.5.3 update 64, Copyright (c) 2012-2019 Simon Nash. All rights reserved.
Enter command (? for help):
>#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x00007ff9ac92a839, pid=7728, tid=0x0000000000000bbc
#
# JRE version: Java(TM) SE Runtime Environment (8.0_241-b07) (build 1.8.0_241-b07)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.241-b07 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [KERNELBASE.dll+0x3a839]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Simon\AppData\Roaming\MinimWatch\lib\hs_err_pid7728.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Is this something you've seen before?
Would you like the contents of hs_err_pid7728.log?
Are there any Windows services that it relies on?

[simoncn]

Please post the hs_err_pid7728.log file. It would be better for me if you could post it as a file attachment rather than inline text. Many thanks.

[simbun]

(16-02-2020 17:11)simoncn Wrote:  Please post the hs_err_pid7728.log file. It would be better for me if you could post it as a file attachment rather than inline text. Many thanks.

Here you go.

[simoncn]

Thanks very much for this. Is there anything in the minimwatch.log file or any minimwatch-crash-.... files?

Also, it looks like you are running 32-bit Java on 64-bit Windows. Can you try uninstalling 32-bit Java and installing 64-bit Java?

[simbun]

I am running 64-bit java, it stated that in the minimwatch.log too

Code:

MinimWatch 0.8.5.3 update 64, Copyright (c) 2012-2019 Simon Nash. All rights reserved.
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode)
Platform default charset is windows-1252
Active subnet is 192.168.20.0

It also stated 64-bit on std out from calling startc.cmd

Code:

Java VM: Java HotSpot(TM) 64-Bit Server VM (25.241-b07 mixed mode windows-amd64 compressed oops)

Just to be absolutely sure I've uninstalled Java and reinstalled 64-bit Java with the same outcome.

I don't have any minimwatch-crash- files.

Don't MinimServer and MinimWatch have the same requirements (of Java at least)?

[simoncn]

I saw these in the hs_err file:

0x00007ff7a65a0000 - 0x00007ff7a65d7000 C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe

PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath

C:\Program Files (x86) is used for 32-bit programs. However, I can see that you are running the 64-bit version of Java.

From the hs_err file, it looks like something has gone wrong when Java code in ohNet tried to call into native C code in ohNet. I have never seen this message before. There are a number of Google hits describing similar errors but nothing that seesm to fit the present circumstances.

MinimWatch calls different parts of ohNet than MinimServer. The crash is in one of those different parts. It appears that ohNet is throwing a C++ exception but unfortunately Java does not capture any information about what exception this is.

My best guess is that there is something about your network adapter configuration that is causing ohNet to throw the exception. Please post the output of ipconfig /all. This should provide more clues.

[simbun]

Both the Pi and Windows machine reside on the same vlan.

Code:

C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Win10Pro
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection
   Physical Address. . . . . . . . . : 54-04-A6-##-##-##
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.20.12(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 16 February 2020 21:51:05
   Lease Expires . . . . . . . . . . : 17 February 2020 21:51:05
   Default Gateway . . . . . . . . . : 192.168.20.1
   DHCP Server . . . . . . . . . . . : 192.168.20.1
   DNS Servers . . . . . . . . . . . : 192.168.20.1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Thanks for taking the time to look into this, I really appreciate it.

[simoncn]

The Ethernet adapter configuration looks normal. Can you say more about what you are doing with VLANs and how your network is set up? If the network is not able to pass multicast messages and/or UPnP messages to/from the Windows machine, this could be causing the problems you are seeing with MinimWatch and MinimServer not working correctly on the Windows machine.

[simoncn]

Please do the following. This will produce a detailed log file showing what is happening during MinimWatch and ohNet startup. I hope this log file will provide more information about what is happening inside ohNet before the error.

1) Create a plain text file named minimwatch.defaults containing the following two lines:

.logLevel = debug
ohnet.debug = All

2) Place this file in the folder C:\Users\your-user-name\AppData\Roaming\MinimWatch\data. This folder also contains the files minimwatch.config and minimwatch.log.

3) Start MinimWatch

4) After MinimWatch has crashed, copy the minimwatch.log file out of the above folder, zip this file and attach it to a post here as a file attachment.

Many thanks for your help with finding the cause of this problem.

[simbun]

Sorry for the delay, I was checking the LAN firewall settings and perfoming some logging (as well as sleeping), but the only event I can see MinimWatch make is to 5.153.222.25.

I'm using vlans just to add some security to the home network. At the moment most of the devices are still on the same vlan (Pi, Windows, BubbleUPnP control point etc) it's only Hikvision security cams and Hue Lights that are separated at the moment (as well as the actual network hardware that's on it's own management vlan).

Find attached the requested log file.