Known issue with Vassal 3.7.8 on M1 Macs?

Unable to run Vassal 3.7.8 on a M1 Mac (not related to the Mac OS security after download). Vassal tries to start for a moment, but then it suddenly exists,

Version 3.7.7 was working fine.

Any known issues?

Any hints in the errorLog?

I am running 3.7.8 on my M1 MacBook Air without any problems.

Here is a part of what I see in the errorLog report:

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue:

Exception Codes: 0x0000000000000001, 0x0000000186ace4e4

Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process: exc handler [2486]

Application Specific Information:
References to Carbon menus are disallowed with AppKit menu system (see rdar://101002625). Use instances of NSMenu and NSMenuItem directly instead.

That definitely doesn’t look like something that would appear in VASSAL’s errorLog. Can you specify what steps you took or what you ran to come up with that output?

OK. Thanks for your help Joel.
I’ll try to erase the older version (3.7.7) and try a fresh install.

That isn’t answering my question, I’d like to understand where that diagnostic output came from. I gave you a link to where VASSAL’s errorlog is stored, but you provided something else. Where did that something else come from? On MacOS, erasing the older version will not have any bearing whatsoever on your ability to run the newer one. We need to figure out why it didn’t work.

Ok. You are really here to help me out. Didn’t want to bother others with this too much. Was just curious to see if other had the same problem…

The report is probably produce by the OS, since it wants to send it to Apple.

I did not notice the link for the Vassal report. Found it. Here is what it says:

2024-02-04 09:13:54,490 [5526-main] INFO VASSAL.launch.StartUp - Starting
2024-02-04 09:13:54,505 [5526-main] INFO VASSAL.launch.StartUp - OS Mac OS X 14.1.2 aarch64
2024-02-04 09:13:54,505 [5526-main] INFO VASSAL.launch.StartUp - Java version 21.0.2
2024-02-04 09:13:54,505 [5526-main] INFO VASSAL.launch.StartUp - Java home /Applications/
2024-02-04 09:13:54,505 [5526-main] INFO VASSAL.launch.StartUp - VASSAL version 3.7.8
2024-02-04 09:13:54,710 [5526-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager

I guarantee you that anyone else in a position to help was going to ask you to supply the VASSAL error log output–was only trying to get you to that point so things can proceed from there. Unfortunately there are no hints in it. That looks like normal output from a successful launch. Maybe the first one was from Java itself crashing.

1 Like

I really want to thank you. Didn’t know about the Vassal report. Learned something today :wink:

You might be right for Java crashing. The Mac OS report started by indicating that:

Translated Report (Full Report Below)

Process: java [2486]
Path: /Applications/
Identifier: java
Version: ???
Code Type: ARM-64 (Native)
Parent Process: launchd [1]

Updated Mac OS Sonoma to 14.3 and it fixed the issue.
My bad.

Thanks again for helping out.


The latest MAC OS for the M3 pro machines is 14.4.1 I
I’m not finding an option to upgrade to 14.4.3 hence VASSAL is not working on my new machine.


14.4.1 is the latest. What problem are you experiencing @jeffmoorenasa ?

The latest vassal versions are not loading on my Mac neither. I had to go back to v3.7.7 to get it to work. Happy to help out with debugging this - just let me know what you need.

We need to know what version of MacOS you’re running and what error messages you see.

I’m running Mac OS Sonoma 14.1 on Apple M2 Pro.

The crash dump I’m getting is as follows:

From the 3.7.10 release notes:

If you are using MacOS 14, please ensure you are using 14.4 or later, to avoid a bug in MacOS which prevents Vassal from starting.

ok, I will try updating my system after hours tonight and will report back on the outcome.