RPi-optimized server crashes on RPi 3 for no apparent reason

I have the VirtualHere server running on a Raspberry Pi 3. Specifically, the latest Raspberry Pi-optimized version. Periodically, the server just crashes for no apparent reason.

Initially, I thought it had to do with the fact that I had the Pi connect to the local network via WLAN. So I swapped the connection and now it's wired. Still the same. Here's an example log:

Feb 20 10:49:23 raspberrypi vhusbdarmpi3[402]: >>> Starting VirtualHere USB Server v3.8.2 (Built: Feb 7 2019, 16:07:11)<<<
Feb 20 10:49:23 raspberrypi vhusbdarmpi3[402]: Using configuration /root/config.ini
Feb 20 10:49:23 raspberrypi vhusbdarmpi3[432]: Using SSL Server certificate at /home/pi/kchan/server.pem
Feb 20 10:49:23 raspberrypi vhusbdarmpi3[432]: Server licensed to=[will provide if prompted] max_devices=unlimited
Feb 20 10:49:23 raspberrypi vhusbdarmpi3[432]: Using large URB's
Feb 20 10:49:23 raspberrypi vhusbdarmpi3[432]: Listening on all network interfaces at TCP SSL port 7574 (IPv6 dual-stack)
Feb 20 10:49:24 raspberrypi vhusbdarmpi3[432]: Found Full speed device [088e:5036] "iLok, iLok" at address 112
Feb 20 10:50:16 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 1
Feb 20 11:10:55 raspberrypi vhusbdarmpi3[432]: Device 112 [088e:5036] BOUND to connection 1
Feb 20 11:29:40 raspberrypi vhusbdarmpi3[432]: Device 112 [088e:5036] UNBOUND from connection 1
Feb 20 11:29:41 raspberrypi vhusbdarmpi3[432]: Unmanaging device 112 [088e:5036]
Feb 20 11:29:41 raspberrypi vhusbdarmpi3[432]: Found Full speed device [088e:5036] "iLok, iLok" at address 112
Feb 20 13:14:23 raspberrypi vhusbdarmpi3[432]: Connection 1 successfully removed (reason:timeout)
Feb 20 13:14:46 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 3
Feb 20 14:16:47 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 4
Feb 20 14:33:45 raspberrypi vhusbdarmpi3[432]: Connection 3 successfully removed (reason:timeout)
Feb 20 14:35:17 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 5
Feb 20 14:52:11 raspberrypi vhusbdarmpi3[432]: Connection 4 successfully removed (reason:timeout)
Feb 20 14:56:50 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 6
Feb 20 14:59:52 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 7
Feb 20 15:02:20 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 8
Feb 20 15:16:31 raspberrypi vhusbdarmpi3[432]: Connection 6 successfully removed (reason:timeout)
Feb 20 15:17:37 raspberrypi vhusbdarmpi3[432]: Connection 5 successfully removed (reason:timeout)
Feb 20 15:18:59 raspberrypi vhusbdarmpi3[432]: Connection 7 successfully removed (reason:timeout)
Feb 20 15:37:50 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 9
Feb 20 15:54:39 raspberrypi vhusbdarmpi3[432]: Connection 8 successfully removed (reason:timeout)
Feb 20 15:56:17 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 10
Feb 20 16:14:32 raspberrypi vhusbdarmpi3[432]: Connection 9 successfully removed (reason:timeout)
Feb 20 17:11:47 raspberrypi vhusbdarmpi3[432]: 192.168.1.155 connected as connection 11
Feb 20 17:28:26 raspberrypi vhusbdarmpi3[432]: Connection 10 successfully removed (reason:timeout)
Feb 20 22:08:46 raspberrypi vhusbdarmpi3[432]: Connection 11 successfully removed (reason:timeout)
Feb 20 22:21:51 raspberrypi vhusbdarmpi3[432]: VirtualHere 3.8.2 caught signal 11 (Segmentation fault) and must exit. Sorry for the inconvenience, please contact mail@virtualhere for help

So far the solution has been to manually restart the service (I do it via sudo reboot). For this I can obviously set up a cron job. But I still think this is not intended behavior. Any support in the matter is appreciated.