KNOWLEDGE BASE
Log In    |    Knowledge Base    |    4D Home
Tech Tip: What is a "Translocated Process"?
PRODUCT: 4D | VERSION: 17 | PLATFORM: Mac OS X
Published On: November 7, 2019

A "Translocated Process" is a process with restricted privileges. The process is referred to as translocated because it runs from a virtual location instead of the actual location the application is installed at. Furthermore, this virtual location that the app is running from only has read only privileges to the disk. Due to this restriction, attempting to do disk operations from the Translocated Process will often result in a crash.

The macOS crash reports created from a translocated process will often give some clues indicating it was a translocated process. For example, look at the Path and Notes in the following crash report:

Process: 4D [24940]
Path: /private/var/folders/*/4D.app/Contents/MacOS/4D
Identifier: com.4d.4d
Version: 17.3 build 17.240828 (17.0.3)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: 4D [24940]
User ID: 501

Date/Time: 2019-10-28 23:23:09.792 -0600
OS Version: Mac OS X 10.14.6 (18G103)
Report Version: 12
Anonymous UUID: 9F2E0E9D-C540-B6B5-EDD5-854533E43423


Time Awake Since Boot: 360000 seconds

System Integrity Protection: enabled

Notes: Translocated Process
...


Specifically the following two lines:
Path: /private/var/folders/*/4D.app/Contents/MacOS/4D
...
Notes: Translocated Process


The Path shows that the application is running from /private/var/folders and the Notes show "Translocated Process". Keep in mind that the application is not installed in the /private/var/folders folder, this is just the translocated path the application is running from.

Typically a 'Translocated Process' is the result of an incorrectly signed application or an application that was installed improperly.

If the translocation process is the result of an improperly installed application then the solution is to reinstall the application.

If the translocated process is the result of am improperly signed application then the application/DMG must be properly signed by the developer before re-attempting to install the application.

Often, re-installation of the signed application from the signed dmg would allow the macOS Gatekeeper to lift the