Original Message:
Sent: 5/10/2024 2:21:00 AM
From: Satid S
Subject: RE: ACS crashing on Mac Pro M2 Windows parallel
Dear Andy
One important factor for run-time stability of IBM i ACS is the Java engine. Since you are using Java engine from Oracle, I suggest you change it to install IBM Semeru JDK for MacOS and use it for IBM i ACS. The latest release of IBM Semeru for MacOS is 21.0.2.
![](https://dw1.s81c.com//IMWUC/MessageImages/e8842e8fca4a4727b75851bb8ed1b5eb.png)
------------------------------
Satid S
------------------------------
Original Message:
Sent: Thu May 09, 2024 01:03 PM
From: Andy Jeffery
Subject: ACS crashing on Mac Pro M2 Windows parallel
I've recently joined and work with Neil, and I to experience the ACS 5250 emulation crashing, my Processor is an Apple M3. Unfortunately it happens extremely regularly and most days it's unworkable :(. It's easy to replicate for myself, simply scroll quickly through a source listing or a subfile page (like WRKACTJOB).
![](https://dw1.s81c.com//IMWUC/MessageImages/ae9e708c93b743b3a22beb7b7ec831cc.png)
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: acslaunch_mac [36354]
Path: /Users/USER/Downloads/*/acslaunch_mac
Identifier: acslaunch_mac
Version: ???
Code Type: ARM-64 (Native)
Parent Process: Exited process [36342]
Responsible: Terminal [4154]
User ID: 501
Date/Time: 2024-05-09 17:48:25.7773 +0100
OS Version: macOS 14.4.1 (23E224)
Report Version: 12
Anonymous UUID: 3C3FD3A9-AF56-3F1A-A456-2B198E326E11
Sleep/Wake UUID: F41BB14B-0558-4BA6-9819-0F51EF214FC8
Time Awake Since Boot: 30000 seconds
Time Since Wake: 12222 seconds
System Integrity Protection: enabled
Crashed Thread: 16 Java: C1 CompilerThread0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: acslaunch_mac [36354]
Application Specific Information:
abort() called
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x18786a1f4 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x18787cb24 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x187872e34 mach_msg_overwrite + 476
3 libsystem_kernel.dylib 0x18786a578 mach_msg + 24
4 CoreFoundation 0x18798a058 __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x18798891c __CFRunLoopRun + 1208
6 CoreFoundation 0x187987e0c CFRunLoopRunSpecific + 608
7 HIToolbox 0x192123000 RunCurrentEventLoopInMode + 292
8 HIToolbox 0x192122e3c ReceiveNextEventCommon + 648
9 HIToolbox 0x192122b94 _BlockUntilNextEventMatchingListInModeWithFilter + 76
10 AppKit 0x18b1e0970 _DPSNextEvent + 660
11 AppKit 0x18b9d2dec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700
12 libosxapp.dylib 0x104a64258 -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 144
13 AppKit 0x18b1d3cb8 -[NSApplication run] + 476
14 libosxapp.dylib 0x104a64010 +[NSApplicationAWT runAWTLoopWithApp:] + 208
15 libawt_lwawt.dylib 0x105648d94 +[AWTStarter starter:headless:] + 488
16 libosxapp.dylib 0x104a65c88 +[ThreadUtilities invokeBlockCopy:] + 28
17 Foundation 0x188ad8914 __NSThreadPerformPerform + 264
18 CoreFoundation 0x187989eb0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
19 CoreFoundation 0x187989e44 __CFRunLoopDoSource0 + 176
20 CoreFoundation 0x187989bb4 __CFRunLoopDoSources0 + 244
21 CoreFoundation 0x1879887a0 __CFRunLoopRun + 828
22 CoreFoundation 0x187987e0c CFRunLoopRunSpecific + 608
23 CoreFoundation 0x187a05e3c CFRunLoopRun + 64
24 acslaunch_mac 0x10469e4a4 0x10469c000 + 9380
25 dyld 0x1875220e0 start + 2360
Thread 1:
0 libsystem_kernel.dylib 0x18786d9ec __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1878ab55c _pthread_cond_wait + 1228
2 libjvm.dylib 0x10646f798 PlatformMonitor::wait(unsigned long long) + 148
3 libjvm.dylib 0x1064309f8 Monitor::wait(unsigned long long) + 128
4 libjvm.dylib 0x1065c92a8 Threads::destroy_vm() + 108
5 libjvm.dylib 0x106170ab4 jni_DestroyJavaVM + 232
6 acslaunch_mac 0x10469ed88 0x10469c000 + 11656
7 acslaunch_mac 0x10469ec38 0x10469c000 + 11320
8 libsystem_pthread.dylib 0x1878aaf94 _pthread_start + 136
9 libsystem_pthread.dylib 0x1878a5d34 thread_start + 8
Thread 2:: Java: GC Thread#0
0 libsystem_kernel.dylib 0x18786a170 semaphore_wait_trap + 8
1 libjvm.dylib 0x1064f74d4 OSXSemaphore::wait() + 24
2 libjvm.dylib 0x106673a88 WorkerThread::run() + 84
3 libjvm.dylib 0x1065bc020 Thread::call_run() + 200
4 libjvm.dylib 0x106467610 thread_native_entry(Thread*) + 344
5 libsystem_pthread.dylib 0x1878aaf94 _pthread_start + 136
6 libsystem_pthread.dylib 0x1878a5d34 thread_start + 8
Thread 3:: Java: G1 Main Marker
0 libsystem_kernel.dylib 0x18786d9ec __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1878ab55c _pthread_cond_wait + 1228
2 libjvm.dylib 0x10646f798 PlatformMonitor::wait(unsigned long long) + 148
3 libjvm.dylib 0x106430960 Monitor::wait_without_safepoint_check(unsigned long long) + 48
4 libjvm.dylib 0x105ffdbe0 G1ConcurrentMarkThread::run_service() + 156
5 libjvm.dylib 0x105f06240 ConcurrentGCThread::run() + 36
6 libjvm.dylib 0x1065bc020 Thread::call_run() + 200
7 libjvm.dylib 0x106467610 thread_native_entry(Thread*) + 344
8 libsystem_pthread.dylib 0x1878aaf94 _pthread_start + 136
9 libsystem_pthread.dylib 0x1878a5d34 thread_start + 8
Thread 4:: Java: G1 Conc#0
0 libsystem_kernel.dylib 0x18786a170 semaphore_wait_trap + 8
1 libjvm.dylib 0x1064f74d4 OSXSemaphore::wait() + 24
2 libjvm.dylib 0x106673a88 WorkerThread::run() + 84
3 libjvm.dylib 0x1065bc020 Thread::call_run() + 200
4 libjvm.dylib 0x106467610 thread_native_entry(Thread*) + 344
5 libsystem_pthread.dylib 0x1878aaf94 _pthread_start + 136
6 libsystem_pthread.dylib 0x1878a5d34 thread_start + 8
Thread 5:: Java: G1 Refine#0
0 libsystem_kernel.dylib 0x18786d9ec __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1878ab55c _pthread_cond_wait + 1228
2 libjvm.dylib 0x10646f808 PlatformMonitor::wait(unsigned long long) + 260
3 libjvm.dylib 0x106430960 Monitor::wait_without_safepoint_check(unsigned long long) + 48
4 libjvm.dylib 0x10600661c G1PrimaryConcurrentRefineThread::wait_for_completed_buffers() + 72
5 libjvm.dylib 0x106006144 G1ConcurrentRefineThread::run_service() + 136
6 libjvm.dylib 0x105f06240 ConcurrentGCThread::run() + 36
7 libjvm.dylib 0x1065bc020 Thread::call_run() + 200
8 libjvm.dylib 0x106467610 thread_native_entry(Thread*) + 344
9 libsystem_pthread.dylib 0x1878aaf94 _pthread_start + 136
10 libsystem_pthread.dylib 0x1878a5d34 thread_start + 8
Regards
Andy
------------------------------
Andy Jeffery
Original Message:
Sent: Mon February 19, 2024 07:00 AM
From: Janus Hertz
Subject: ACS crashing on Mac Pro M2 Windows parallel
Hi Neil
Sorry to hear you still have issues with ACS and 5250 emulation on your Mac.
Please verify that you are using the latest version of ACS (currently 1.1.9.4).
Download from here: https://www.ibm.com/support/pages/ibm-i-access-client-solutions
If your problems continues, I suggest you open an IBM support case for IBM i ACS at https://www.ibm.com/mysupport/
------------------------------
Janus Hertz
Consulting IT Specialist - IBM Power / IBM i - Virtualization, Security, HA/DR.
IBM Northern Europe
Original Message:
Sent: Mon February 19, 2024 06:31 AM
From: Neil Taylor
Subject: ACS crashing on Mac Pro M2 Windows parallel
Hi Janus
Thanks for your reply. You're absolutely right - my mistake, I am running ACS natively on MacOS. The problem is still occurring.
------------------------------
Neil Taylor
Original Message:
Sent: Mon September 04, 2023 07:47 AM
From: Janus Hertz
Subject: ACS crashing on Mac Pro M2 Windows parallel
Hi Neil
Just out of curiosity, why run IBM i ACS on a VM with Windows for ARM (not x86), when you can run ACS perfectly on native MacOS ??
I don't think there has been much testing of ACS on Windows for ARM - if any at all.
Remember Apple CPUs M1 & M2 are ARM processors, not x86 like used in previous Apple Macbooks.
Best Regards,
------------------------------
Janus Hertz
Consulting IT Specialist - IBM Power / IBM i - Virtualization, Security, HA/DR.
IBM Northern Europe
Original Message:
Sent: Thu August 31, 2023 05:43 AM
From: Neil Taylor
Subject: ACS crashing on Mac Pro M2 Windows parallel
Hi
My company has given me a Mac Pro M2 for development work. ACS is running on a Windows Parallel partition on the Mac. ACS is constantly crashing on the 5250 emulator, which is a pain. I've tried playing with the settings on the menu's, but nothing seems to help. My colleague who is also using a Mac Pro M2 is having the same problem.
Does anyone know what settings would prevent this?
Thank you.
------------------------------
Neil Taylor
------------------------------