You are here

Home » Forums » VESC Tool

VESC Tool Crashing on connection (on Macbook version)

3 posts / 0 new
Log in or register to post comments
Last post
Thu, 2025-07-31 00:00
#1
svelte.ca
Offline
Last seen: 1 month 3 weeks ago
VESC Silver
Joined: 2025-07-30 23:38
Posts: 2
VESC Tool Crashing on connection (on Macbook version)

hi - I just donated for a silver release of the VESC tool, and after installing it's crashing when I try to connect to my board (a floatwheel ADV1 with the ADV2 hardware kit installed) 

Is there a logs folder I can investigate what's going wrong? Thanks 

Top
Thu, 2025-07-31 00:09
svelte.ca
Offline
Last seen: 1 month 3 weeks ago
VESC Silver
Joined: 2025-07-30 23:38
Posts: 2

It's crashing here. The repo steps are: 

1. scan for devices (my wheel shows up fine).
2. click connect - crash to desktop. Looking at the crash report it shows -   

Crashed Thread:        32  Dispatch queue: com.apple.bluetooth.iobluetooth.coordinatorQueue

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000d4
Exception Codes:       0x0000000000000001, 0x00000000000000d4

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [3072]

 
 

Top
Thu, 2025-09-18 17:19
etavav
Offline
Last seen: 1 day 15 hours ago
VESC Free
Joined: 2025-09-15 05:30
Posts: 2

Same issue: MacBook M1, latest(downloaded 18.09.2025) Vesc Tool:
 

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               VESC Tool [1080]
Path:                  /Volumes/*/VESC Tool.app/Contents/MacOS/VESC Tool
Identifier:            com.vesc.vesc-tool-3.01
Version:               ???
Code Type:             X86-64 (Translated)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2025-09-18 22:13:14.5262 +0700
OS Version:            macOS 13.7 (22H123)
Report Version:        12
Anonymous UUID:        DC5B8CD1-~~~~~~-4859-3EB2-~~~~~~~~~~~~


Time Awake Since Boot: 440 seconds

System Integrity Protection: enabled

Crashed Thread:        3  Dispatch queue: com.apple.bluetooth.iobluetooth.coordinatorQueue

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000000000000080b
Exception Codes:       0x0000000000000001, 0x000000000000080b

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [1080]

VM Region Info: 0x80b is not in any region.  Bytes before following region: 140722811336693
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      mapped file              7ffc952e8000-7ffca8880000 [309.6M] r-x/r-x SM=COW  ...t_id=d3efa6e1

Thread 0::  Dispatch queue: com.apple.main-thread

And 5 minutes ago it was working. I did nothing big. And it's working from windows PC.
I have two M1, on second same issue. Suddenly always crush after pressing connect on Bluetooth.
Cleaning with AppCleaner does not help.

Please fix it.

Top