VirtualHere client on MacOS Sequoia crashing (Namespace SIGNAL, Code 6 Abort trap: 6)

Hi, I'm trying to get VirtualHere working on my MacOS host (m1) and client (m3). However on both systems, the client crashes when opening.
 

I see this in the console.app:
Crashed Thread:        13

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   VirtualHereUniversal [44242]

Application Specific Information:
stack buffer overflow
 

Any idea what is causing this? Since it happens on bith systems, I assume it's something in the code of the client?

Thanks!
 

#3

Thanks for reaching out this quickly. I read the thread, but doesn't sound familiar. The advice in the thread was contacting the developer: "When problem occurs in only one Application, that suggest the problem is inside that Application. Best advice in that case is to contact the developer and see if they can provide additional guidance."

Also the second issue in the thread was fixed by updating the application.


The m1 Mac is a recent clean install with only three applications:
 - Chrome (no extensions)
 - Minecraft Education (the device is not managed, just regular download)
 - Parsec

Any know culprits that you know of in this list?

The m3 Mac has more applications installed, but also nothing like VPN/Cleaners/Optimizers etc. I haven't seen this with any other program. 
Also the client quits right at opening, not after a specific time (like I would expect when it builds up some memory issue). It does this when no other programs are running, on an idle system.

The m1 is running Sequoia 15.3.2

The m3 is running Sequoia 15.4.1 

If you can't replicate the issue, it will be hard to find the cause probably. Not sure what I can try next.
 

** Update: I just updated my m1 from 15.3.2 to 15.5, still same problem

#4

Is there any stack trace in the crashdump? Or does it just end with "Stack Buffer Overflow"

#5

I'm not that familiar with the console.app in MacOS.

Is says thread 12 (sometimes 12, sometimes 13, this last time is was 12) crashed, and there is info about thread 12, I assume this line is the cause of the issue: 0x185b54aec __stack_chk_fail + 96:

Thread 12 Crashed:
0   libsystem_kernel.dylib                   0x185c21388 __pthread_kill + 8
1   libsystem_pthread.dylib                  0x185c5a88c pthread_kill + 296
2   libsystem_c.dylib                        0x185b63cf0 __abort + 132
3   libsystem_c.dylib                        0x185b54aec __stack_chk_fail + 96
4   VirtualHereUniversal                     0x104d2bfd0 0x104b2c000 + 2097104
5   libsystem_dnssd.dylib                    0x193e92b58 handle_resolve_response + 316
6   libsystem_dnssd.dylib                    0x193e8fb80 DNSServiceProcessResult + 660
7   VirtualHereUniversal                     0x104d2b590 0x104b2c000 + 2094480
8   libsystem_dnssd.dylib                    0x193e907d0 handle_browse_response + 336
9   libsystem_dnssd.dylib                    0x193e8fb80 DNSServiceProcessResult + 660
10  VirtualHereUniversal                     0x104d2aa58 0x104b2c000 + 2091608
11  VirtualHereUniversal                     0x104d2b234 0x104b2c000 + 2093620
12  libsystem_pthread.dylib                  0x185c5ac0c _pthread_start + 136
13  libsystem_pthread.dylib                  0x185c55b80 thread_start + 8
 

Thread 12 crashed with ARM Thread State (64-bit):
   x0: 0x0000000000000000   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000000000000
   x4: 0x0000000000000000   x5: 0x0000000000000000   x6: 0x0000000000000000   x7: 0x0000000185b6aa9a
   x8: 0xa9e10b61b4e78fbf   x9: 0xa9e10b60df727fbf  x10: 0x0000000000000000  x11: 0x0000000000001180
  x12: 0x00000000000007fb  x13: 0x00000000000007fd  x14: 0x0000000033800839  x15: 0x00000000336000bf
  x16: 0x0000000000000148  x17: 0x00000001f4db9fa8  x18: 0x0000000000000000  x19: 0x0000000000000006
  x20: 0x0000000000013503  x21: 0x000000016b95f0e0  x22: 0x0000000000001e00  x23: 0x000000016b95d710
  x24: 0x0000000000000003  x25: 0x0000000000000053  x26: 0x000060000182e7fc  x27: 0x000060000182e7e0
  x28: 0x000060000182e7fc   fp: 0x000000016b95d640   lr: 0x0000000185c5a88c
   sp: 0x000000016b95d620   pc: 0x0000000185c21388 cpsr: 0x40001000
  far: 0x0000000000000000  esr: 0x56000080  Address size fault


I don't think the other information is relevant, but just in case:

Binary Images:
      0x104b2c000 -        0x106187fff com.virtualhere.client (5.8.7) <cfc50563-bbdc-31c3-93e5-96cabc100a31> /Users/USER/Desktop/VirtualHereUniversal.app/Contents/MacOS/VirtualHereUniversal
      0x10c1cc000 -        0x10c1d7fff libobjc-trampolines.dylib (*) <d02a05cb-6440-3e7e-a02f-931734cab666> /usr/lib/libobjc-trampolines.dylib
      0x118000000 -        0x118693fff com.apple.AGXMetal13-3 (327.5) <bea42a86-a627-3c22-8eec-738c406242ff> /System/Library/Extensions/AGXMetal13_3.bundle/Contents/MacOS/AGXMetal13_3
      0x185cc9000 -        0x186207fff com.apple.CoreFoundation (6.9) <df489a59-b4f6-32b8-9bb4-9b832960aa52> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
      0x191715000 -        0x191a1bfdf com.apple.HIToolbox (2.1.1) <9286e29f-fcee-31d0-acea-2842ea23bedf> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
      0x189c31000 -        0x18b0c2c7f com.apple.AppKit (6.9) <5d0da1bd-412c-3ed8-84e9-40ca62fe7b42> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
      0x1858b4000 -        0x18594f4cf dyld (*) <9cf0401a-a938-389e-a77d-9e9608076ccf> /usr/lib/dyld
              0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
      0x185c18000 -        0x185c53653 libsystem_kernel.dylib (*) <60485b6f-67e5-38c1-aec9-efd6031ff166> /usr/lib/system/libsystem_kernel.dylib
      0x185c54000 -        0x185c60a47 libsystem_pthread.dylib (*) <647b91fc-96d3-3bbb-af08-970df45257c8> /usr/lib/system/libsystem_pthread.dylib
      0x185aeb000 -        0x185b6c46f libsystem_c.dylib (*) <f4529d5e-24f3-3bbb-bd3c-984856875fc8> /usr/lib/system/libsystem_c.dylib
      0x1912be000 -        0x1912e5ddf com.apple.audio.caulk (1.0) <5ce1b98f-c512-379d-9a42-5cce5923bf9d> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk
      0x193e8e000 -        0x193e96d57 libsystem_dnssd.dylib (*) <82c69999-6ede-35a7-a08e-79714aa45517> /usr/lib/system/libsystem_dnssd.dylib
      0x185b6d000 -        0x185bf9ff7 libc++.1.dylib (*) <875203a1-087b-33a6-93a5-928bb7e9114c> /usr/lib/libc++.1.dylib

External Modification Summary:
 Calls made by other processes targeting this process:
   task_for_pid: 0
   thread_create: 0
   thread_set_state: 0
 Calls made by this process:
   task_for_pid: 0
   thread_create: 0
   thread_set_state: 0
 Calls made by all processes on this machine:
   task_for_pid: 0
   thread_create: 0
   thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=1.7G resident=0K(0%) swapped_out_or_unallocated=1.7G(100%)
Writable regions: Total=1.2G written=642K(0%) resident=642K(0%) swapped_out=0K(0%) unallocated=1.2G(100%)

                               VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Accelerate framework               128K        1 
Activity Tracing                   256K        1 
CG image                           832K       13 
CG raster data                      80K        1 
ColorSync                          560K       27 
CoreAnimation                      880K       13 
CoreGraphics                        32K        2 
CoreUI image data                  720K       10 
Foundation                          32K        2 
Kernel Alloc Once                   32K        1 
MALLOC                             1.2G       48 
MALLOC guard page                  288K       18 
STACK GUARD                       56.3M       18 
Stack                             17.0M       18 
VM_ALLOCATE                        192K        5 
__AUTH                            5363K      686 
__AUTH_CONST                      75.6M      926 
__CTF                               824        1 
__DATA                            25.4M      903 
__DATA_CONST                      27.5M      935 
__DATA_DIRTY                      2763K      335 
__FONT_DATA                        2352        1 
__

#6

I also tried running the app in Rosetta, just to check if it was ARM related, but same issue there for me.

#8

I downloaded and ran the software, same issue, and I don't see much difference in the console.app.
I also tried tun run it via terminal:
open ./VirtualHereUniversal.app

This quits without any message.

And:
./VirtualHereUniversal.app/Contents/MacOS/VirtualHereUniversal

quits with: zsh: abort      ./VirtualHereUniversal.app/Contents/MacOS/VirtualHereUniversal

So no extra info there.
 

I put the full console log on filebin: https://filebin.net/j88ehbbjyxyzx5lc


Output in Console:


Process:               VirtualHereUniversal [35772]
Path:                  /Users/USER/Desktop/VirtualHereUniversal.app/Contents/MacOS/VirtualHereUniversal
Identifier:            com.virtualhere.client
Version:               5.8.7 (5.8.7)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2025-05-20 15:31:34.6532 +0200
OS Version:            macOS 15.4.1 (24E263)
Report Version:        12
Anonymous UUID:        3C565A7A-8045-7139-BAE4-7DD5DA5E5572

Sleep/Wake UUID:       F760F9B2-A35A-471C-9665-5568A0219C85

Time Awake Since Boot: 710000 seconds
Time Since Wake:       23431 seconds

System Integrity Protection: enabled

Crashed Thread:        12

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   VirtualHereUniversal [35772]

Application Specific Information:
stack buffer overflow

 


Thread 12 Crashed:
0   libsystem_kernel.dylib                   0x194d9c388 __pthread_kill + 8
1   libsystem_pthread.dylib                  0x194dd588c pthread_kill + 296
2   libsystem_c.dylib                        0x194cdecf0 __abort + 132
3   libsystem_c.dylib                        0x194ccfaec __stack_chk_fail + 96
4   VirtualHereUniversal                     0x100acae0c dnsServiceResolveReply(_DNSServiceRef_t*, unsigned int, unsigned int, int, char const*, char const*, unsigned short, unsigned short, unsigned char const*, void*) + 940
5   libsystem_dnssd.dylib                    0x1a2d24b58 handle_resolve_response + 316
 

Thread 12 crashed with ARM Thread State (64-bit):
   x0: 0x0000000000000000   x1: 0x0000000000000000   x2: 0x0000000000000000   x3: 0x0000000000000000
   x4: 0x0000000000000000   x5: 0x0000000000000000   x6: 0x0000000000000000   x7: 0x0000000194ce5a9a
   x8: 0x574980ec8a253d3f   x9: 0x574980ede59f0d3f  x10: 0x00000000000000cb  x11: 0x0000000000002760
  x12: 0x00000000000007fb  x13: 0x00000000000007fd  x14: 0x00000000a661a07f  x15: 0x00000000a6419899
  x16: 0x0000000000000148  x17: 0x0000000204d18ac0  x18: 0x0000000000000000  x19: 0x0000000000000006
  x20: 0x0000000000017203  x21: 0x000000016fba30e0  x22: 0x0000600001b49c00  x23: 0x0000600001b49b60
  x24: 0x000000000000001e  x25: 0x0000000000000000  x26: 0x0000000000000001  x27: 0x0000000000000008
  x28: 0x0000000000000000   fp: 0x000000016fba0bf0   lr: 0x0000000194dd588c
   sp: 0x000000016fba0bd0   pc: 0x0000000194d9c388 cpsr: 0x40001000
  far: 0x0000000000000000  esr: 0x56000080  Address size fault

#9

Thanks for that. The virtualhere app is crashing in the part which Automatically finds a USB server on the network.

Could you try this:

Edit the file /Users/<username>/Library/Preferences/vhui Preferences

under the [General] section add the line

AutoFind=0

Then save the file, and start the client. Is it ok now? 

Try specifying the IP address of the virtualhere server by right clicking USB Servers->Specify Server->Add and put in the IP address of the virtualhere server. If its a Synology machine you need to specify the :17570 port otherwise no port needs to be specified 

#10

Yes, that did it! I have to test the connection to the server, since I'm not at home at the moment, but the client doesn't crash now.
Any idea why this is happening on both of my systems, but not on your Mac?
Is it something in my network that is broadcasting something unexpected?

Thanks for helping out and finding the solution. Do you expect in future updates I can enable autofind again?

#12

This is weird. On my M3 Macbook it's working now with AutoFind = 1.
However on my M1, it's not working when enabling AutoFind (when enabling in menu, it quits right away, when starting again, it doesn't work until I update the preference file to disable auto find).

Crash report from the M1:
https://filebin.net/yzdxlcj9nm7ztjk5

Thread 16 Crashed:
0   ???                                   0x7ff8a808eae0 ???
1   libsystem_kernel.dylib                0x7ff81ab23846 __pthread_kill + 10
2   libsystem_pthread.dylib               0x7ff81ab5eb16 pthread_kill + 259
3   libsystem_c.dylib                     0x7ff81aa7d7de __abort + 145
4   libsystem_c.dylib                     0x7ff81aa6aff9 __stack_chk_fail + 102
5   VirtualHereUniversal                     0x100c4a711 dnsServiceResolveReply(_DNSServiceRef_t*, unsigned int, unsigned int, int, char const*, char const*, unsigned short, unsigned short, unsigned char const*, void*) + 1153
6   ???                                   0x666a64504b72 ???

** update: 
I tried to download and install the new version twice, just to be sure I was not using the old version.
The M1 is on OS 15.5, the M3 still on 15.4.1

#13

There is some strange setting on your machine.

The latest ips stack trace shows that its running the x86_64 version of the binary via rosetta even though your machine is an M1 Apple Silicon?

 

#14

Sorry, my mistake, the flag 'Open in rosetta' was still set. I assumed it was removed when deleting the app, but it was still there for the new app.
However, without rosetta toggled on, same issue on the M1. (and the M3 is working with either rosetta turned on or off).

Here is the new output with rosetta turned off:
https://filebin.net/8uyr9q175zh79z5d

#15

Thanks for the trace its a bit more helpful. I can see a line number in the crash now but its not particularly useful. Is it possible to use e.g RustDesk or Anydesk for a few minutes while you are there to run it under a debugger? If so email me mail [at] virtualhere.com (mail[at]virtualhere[dot]com)