NX client core files filling up directory on OSX 10.11.3

[gran0260]

I recently installed NX client version 5.0.53 on a late-2015 Macbook Pro running OSX 10.11.3. My 1TB hard drive proceeded to fill up over the course of the last week with core dumps behind the scenes (about 700GB of core dump files). I checked in the console application for error messages occurring around the times of the core dumps and they are related to NoMachine which is bizarre since I was not running the application at that time (I haven’t used it since a week ago, 1-25-16). I’m attaching the zip archive of my ~/.nx directory. Is this a bug or have I done something wrong?

Attachments:

1. nxdir.zip

[Britgirl]

Hi, can you tell us if updating to .63 fixes the problem?

[carlilek]

Same issue here with 10.11.4 and latest download of NoMachine (5.1.9_16)

Attachments:

1. nx.zip

[carlilek]

Also these errors repeatedly in system log:

3/22/16 4:16:15.176 PM com.apple.xpc.launchd[1]: (com.nomachine.localnxserver) Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

3/22/16 4:16:25.795 PM com.apple.xpc.launchd[1]: (com.nomachine.localnxserver[11351]) Service exited due to signal: Abort trap: 6

 

[Britgirl]

A look at the logs indicates that this is not the same problem. It looks like a server problem. I suggest you open a new topic with the details so we keep investigations separate. We’ll most likely need logs, but they must be full set of logs from the affected Mac, along with the crash report (those logs that you sent us indicate the path where the crash report is located).

Instructions for debug logs are here: https://www.nomachine.com/DT07M00098

First, please submit a new topic.

[Author]

Posts