MacOS crashes and slowness
Neil
11-28-19
We are seeing many client crashes per day after switching to 8.5 2019-09-15. Server and clients are running MacOS Catalina. Server and client are both on the same local network.

Crashes can be triggered from just about anything such as browsing for a client or item, running maintenance, etc. Loading up a client list can sometimes take 5-10 seconds. Every client experiences the crashes.

Nothing unusual on the client or server log. Client log shows as follows during a crash:

2019-11-27 10:07:46 ES1 Polling server, sendlevel=0, replyf=1
2019-11-27 10:09:13 *** running with new mail receiving and parsing ***
2019-11-27 10:09:13 *** Using Clock Replacement ***
2019-11-27 10:09:14 Last session was not properly terminated
2019-11-27 10:09:14 *** using a freelist to keep track of free space ***
2019-11-27 10:09:21 Database ID is: CC5F9E7D7C40698F5C353BC243EA9A82

2019-11-27 10:09:59 ES1 8.5 2019-09-15 (build 85321027)

During a crash the client hangs for a while then exists with a quit unexpectedly MacOS error.

Exception Type: EXC_BAD_ACCESS (SIGSEV)
Exception Codes: KERN_INVALID_ADDRESS AT 0x00000000000000670
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11


One of the clients also has had a missing hansa.hct a couple times after a crash necessitating a reinstall.


Just checking if anyone else has run into something similar.

Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
Arzu Erdogdu
Hello! You can mark it as closed as option. If document is connected with other documents you can not delete it so you will not be able to delete PO, as you will not be able to remove Goods receipt...
09:29 13 Jun 2025
Paul Timms
Hi Yavuz The Services Cache register is stored on the server. Our customer servers are either Linux or Windows. The client OS is irrelevant. Thanks Paul...
14:44 10 Jun 2025