macOS client 5.4.6 crash

Submitted by Libramale on #1

I just upgraded to latest macOS 12/13 client and Linux (RPi3+ optimised 32bit) server.
When opening a session using Serial the client immediately crashes.

Any chance for a copy of the previous client so I can continue working until fixed?

Please.

 

André

Submitted by Michael on Wed, 2023/04/05 - 09:04

#2

Thanks for letting me know,, I have rolled back to 5.4.5 . Download it again from this website

 

Submitted by Michael on Thu, 2023/04/06 - 23:20

#3

Ive updated the client to 5.4.7 which some bug fixes and a resolution to your issue. Could you download and try that version.

Submitted by Libramale on Fri, 2023/04/07 - 00:20

#4

Have tried twice to download, still showing 5.4.6 on website, download and install also show it as 5.4.6.

 

Submitted by Libramale on Fri, 2023/04/07 - 00:21

#5

Apologies, looked at the server side, confused I am..
Will try 5.4.7 client now

Submitted by Libramale on Fri, 2023/04/07 - 00:28

#6

Just tried with 3 devices, console access working fine.
Will test with firmware flash update bit later..

 

Submitted by Michael on Fri, 2023/04/07 - 06:09

#7

Thanks for letting me know

Submitted by Libramale on Fri, 2023/06/30 - 17:37

#8

Hi Michael,

Error message with latest versions. Happens once or twice per day, nothing specific I can say trigger it.

Once the error has occurred all USB ports disappear from the list in Serial 2.0.15.

To fix the error I must quit VH and select "Yes" to a prompt saying that "You are still using USB devices. Are you sure you want to quit?"

After restarting VH the device immediately appears in the Serial list once connected in VH.

Andre

 

 

2023-06-30 09:24:25 INFO  :VirtualHere Client 5.5.3 starting (Compiled: Jun  7 2023 11:54:15)
2023-06-30 09:24:25 INFO  :Client OS is macOS Ventura Version 13.4.1 (Build 22F82)
2023-06-30 09:24:25 INFO  :Using config at /Users/andremaree/Library/Preferences/vhui Preferences
2023-06-30 09:24:25 INFO  :IPC available at /tmp/vhclient
2023-06-30 09:24:25 INFO  :Auto-find using Bonjour - on
2023-06-30 09:24:25 INFO  :Auto-find using Bonjour SSL - on
2023-06-30 09:24:31 INFO  :interestHandler mt=3758096641
2023-06-30 09:26:16 ERROR :interestHandler kUSBHostMessageControllerException 0x5. PLEASE EXIT AND RESTART THIS CLIENT
2023-06-30 09:26:16 INFO  :interestHandler mt=3758096656
 

Submitted by Michael on Fri, 2023/06/30 - 20:25

#9

Ok thats a tough one, ill add it to my todo list to investigate...

Submitted by Libramale on Sat, 2023/07/01 - 19:14

#10

 

Just happened again, connected to device in background but have not done anything for >30min.

 

2023-06-30 09:36:33 INFO  :VirtualHere Client 5.5.3 starting (Compiled: Jun  7 2023 11:54:15)
2023-06-30 09:36:33 INFO  :Client OS is macOS Ventura Version 13.4.1 (Build 22F82)
2023-06-30 09:36:33 INFO  :Using config at /Users/andremaree/Library/Preferences/vhui Preferences
2023-06-30 09:36:33 INFO  :IPC available at /tmp/vhclient
2023-06-30 09:36:33 INFO  :Auto-find using Bonjour - on
2023-06-30 09:36:33 INFO  :Auto-find using Bonjour SSL - on
2023-06-30 09:36:41 INFO  :interestHandler mt=3758096641
2023-06-30 12:27:53 INFO  :Connection 2 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-06-30 12:27:53 INFO  :Connection 1 remotely disconnected gracefully (rx)
2023-06-30 17:39:42 INFO  :Server ping timeout, shutting down connection 3...
2023-06-30 17:39:42 INFO  :Connection 3 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-06-30 17:39:49 INFO  :Connection 5 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-06-30 17:39:49 INFO  :Connection 4 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-07-01 10:09:33 INFO  :Error 'nodename nor servname provided, or not known' getaddrinfo failed for gw.maree.us:7575
2023-07-01 11:08:50 INFO  :Connection 7 remotely disconnected gracefully (rx)
2023-07-01 11:08:58 ERROR :interestHandler kUSBHostMessageControllerException 0x5. PLEASE EXIT AND RESTART THIS CLIENT
2023-07-01 11:08:58 INFO  :interestHandler mt=3758096656
2023-07-01 11:09:02 INFO  :assert:../src/common/event.cpp,1930,SearchDynamicEventTable,nNew != dynamicEvents.size(),
2023-07-01 11:09:02 INFO  :Server ping timeout, shutting down connection 7...
 

Submitted by Michael on Sat, 2023/07/01 - 22:06

#11

Next time it happens can you run this from the Terminal (assuming it happened less than 5 minutes ago)

sudo log show --last 5m > out.log

and send me the out.log file

Submitted by Libramale on Thu, 2023/07/06 - 21:37

#12

Log is big, 16MB, can I email to you

Submitted by Libramale on Mon, 2023/07/10 - 20:31

#13

Have tried the fix suggested, same problem

Submitted by Michael on Mon, 2023/07/10 - 21:35

#14

What serial <->usb device are you using? An FTDI or SiLabs?  I will try to reproduce here. What is your setup exactly.

Submitted by Libramale on Mon, 2023/07/10 - 21:54

#15

I use the USB server to access 4 MCU based development devices.

Have 2x FTDI 2323 and 2x CH340 devices connected.

The error occurs various stages ie connected but doing nothing or in process of being disconnected.

I have not been able to see any pattern relating to FTDI vs CH340, crash seems to occur with both.

 

Only thing that might be of interest/importance:

I use a hairpin NAT config on my firewall to make the USB server accessible, using the exact same URL (tbdev.domain.tld:7575), from both the LAN and externally when travelling. So, when at home the USB server is listed twice (192.168.1.5:7575 and tbdev.domain.tld:7575) whereas externally it is only seen as tbdev.domain.tld:7575.

 

Submitted by Michael on Tue, 2023/07/11 - 09:08

#16

OK i have a CH340 and a some FTDI devices ill test with and let you know...

Submitted by Michael on Wed, 2023/07/12 - 14:18

#17

Can you download and run this new version. It has a lot more logging for deadlocks and other issues.

https://www.virtualhere.com/sites/default/files/usbclient/test/VirtualH…

When it crashes, can you send me the contents of USB Hubs->System Messages from the client because it should have extra information in there.

( I tried serialio with my FTDI adapter for 8+ hours with no problems yesterday . Ive had to reorder a CH340 as mine is lost)

Submitted by Libramale on Wed, 2023/07/12 - 17:28

#18

Some updated info.

#1 Problem definitely related to CD34x chips, tried in a planned manner with 2x FTDI and 2xCH340 connected, only happened with CH340

#2 Installed new version BUT, new/beta VH client terminates automatically, without any error message when I try to close the Serial terminal session, after having disconnected the connection within Serial.

#3 I just confirmed again, the automatic termination of the VH client ONLY happens when the Serial connection being disconnected/closed was to a CH340 device. With a TDI device the VH client stays open and connected, no error message despite number dis/connect activities to FTDI devices

 

 

 

Submitted by Michael on Wed, 2023/07/12 - 18:01

#19

OK i have to wait a few days for my CH340 to arrive...

Submitted by Michael on Tue, 2023/07/25 - 11:17

#20

This should be resolved in 5.5.4 of the client now

Submitted by Libramale on Sun, 2023/08/13 - 06:41

#21

I have been running the latest version for last 2 days, worked fine until now. Error as below. If you need more info just let me know.

Andre

 

2023-08-12 13:00:44 INFO  :VirtualHere Client 5.5.4 starting (Compiled: Jul 25 2023 09:58:35)
2023-08-12 13:00:44 INFO  :Client OS is macOS Ventura Version 13.5 (Build 22G74)
2023-08-12 13:00:44 INFO  :Using config at /Users/andremaree/Library/Preferences/vhui Preferences
2023-08-12 13:00:44 INFO  :IPC available at /tmp/vhclient
2023-08-12 13:00:49 INFO  :interestHandler mt=3758096641
2023-08-12 13:58:44 INFO  :Connection 1 remotely disconnected gracefully (rx)
2023-08-12 13:58:53 INFO  :assert:../src/common/event.cpp,1930,SearchDynamicEventTable,nNew != dynamicEvents.size(),
2023-08-12 13:58:53 INFO  :Server ping timeout, shutting down connection 1...
2023-08-12 15:18:47 INFO  :Server ping timeout, shutting down connection 3...
2023-08-12 15:18:47 INFO  :Connection 3 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-08-12 15:19:03 INFO  :Could not connect to 72davies.irmacos.com:17575
2023-08-12 15:19:33 INFO  :Could not connect to 72davies.irmacos.com:17575
2023-08-12 16:18:30 INFO  :Connection 2 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-08-12 16:18:30 INFO  :Connection 6 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-08-12 16:19:31 INFO  :Connection 7 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-08-12 16:19:31 INFO  :Connection 8 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-08-12 16:25:45 INFO  :Retrying to use device at address 112 on server vh-rem2 (72davies.irmacos.com:17575), the previous bind failed with an error (see server log)
2023-08-12 18:00:11 INFO  :Connection 10 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-08-12 18:00:11 INFO  :Connection 9 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-08-12 18:01:12 INFO  :Connection 12 remotely disconnected gracefully (rx)
2023-08-12 18:01:12 INFO  :Connection 11 receiving msg size didnt complete due to error 9, Bad file descriptor
2023-08-12 18:21:44 INFO  :Warning: Port 1 failed to reset (error -1)
2023-08-12 18:52:26 INFO  :Warning, error aborting ep 0x02 for device 112, -19
2023-08-12 18:52:26 INFO  :Warning, error clearing halt on ep 0x81 for device 112, -19
2023-08-12 18:52:26 INFO  :Warning, error clearing halt on ep 0x82 for device 112, -19
2023-08-12 22:36:35 INFO  :Timed out waiting for ep 0x82 to quiesce
2023-08-12 22:36:36 INFO  :Error enqueuing ep 0x82 ack, error -536870174  Transfer completion message was not sent. (The current endpoint state Paused cannot generate transfer completions.)
2023-08-12 22:36:36 INFO  :ep 0x81 PAUSE respondToCommand returned error -536870174 , Command cannot be processed successfully. (Command cannot be processed in the current state.)
2023-08-12 22:36:43 ERROR :interestHandler kUSBHostMessageControllerException 0x5. PLEASE EXIT AND RESTART THIS CLIENT
2023-08-12 22:36:43 INFO  :interestHandler mt=3758096656
 

Submitted by Michael on Sun, 2023/08/13 - 07:45

#22

What USB device is not working recently? I cant tell from the log

Submitted by Michael on Sun, 2023/08/13 - 08:44

#24

You will need to look on the server side and see the error. I think there might be some power problem. Since nothing has changed with virtualhere or macos then it must be some hardware issue.

Submitted by Libramale on Fri, 2023/09/15 - 22:10

#25

Allow sizing of windows to make all options visible. For example "Advanced Setting" not all options are readable.

Since I work with local and remote USB device, and do so from local and remote sites, I have each USB server (normally accessed remotely but sometimes local to the device) defined under "Specify Hubs". This results in the client searching for them every 30sec causing the main client screen to refresh showing 2 or 3 "Connecting to USB Hub..." messages at the top, with all existing devices shifting down 2 or 3 lines. Numerous times this has happened at the exact point where I am selecting a device to connect to resulting in the wrong device being selected. Maybe do the refresh message to the bottom, and add newly found devices at the bottom?

CH340 driver still a problem. Out of 10 different device models only 3 types have CH340 chips and these devices are 100% consistently the only ones causing the client to crash on disconnect specifically.

Will email logs to you, just let me know what else you would like and I will try.

Submitted by Michael on Sat, 2023/09/16 - 10:45

#26

Thanks for the logs, and suggestions. I made a change so that the Advanced Settings... is resizable, and "Connecting to Hub" always appears at the bottom and wont disrupt the order of the Device tree.

and i found the bug in the client which might fix the ch340 issue. Can you exit the virtualhere client if it currently running, then download and run this new beta version.

https://www.virtualhere.com/sites/default/files/usbclient/test/VirtualH…

Let me know how it goes.

Submitted by Libramale on Thu, 2023/09/21 - 19:11

#27

Seems problem still there, still consistent on CH340 devices.

Other 2 problem are fixed, thanks.

Log following via email

Submitted by Michael on Thu, 2023/09/21 - 20:46

#28

Can you tell me the USB Vendor Id/Product Id of your CH340 device? You can find this in the VirtualHere client, by right clicking on the Device and selecting Properties.

I have a CH340 with a VID 1A86 and PID of 7523 i use for testing

Edit: Never mind, found it in the logs its the same chip but slightly newer revision