Segmentation Fault Error

In some rare cases, one of our products may crash and display a segmentation fault error. These errors can be challenging to diagnose, as they can stem from various underlying causes such as faulty memory access, external library issues, or unexpected runtime conditions.

A segmentation fault occurs when a program tries to access a memory region that it’s not permitted to use, or when it attempts an invalid operation on a valid memory region, such as writing to a read-only area or overwriting part of the operating system. — Wikipedia.

Table of Contents

What the Error Looks Like

An example of the a Segmentation Fault error will display the below, typically within the applications terminal.

Segmentation fault (core dumped)

Possible Resolution Steps

Some ways to resolve the segmentation fault error include following the below steps. However, if there's an issue further or with the host the issue will likely persist over time.

1. Ensure the product is not running

2. Delete the package-lock.json file and node_modules folder in the products installation directory

3. Rebuild node's package manager by running cd /home/faxstore && npm rebuild (change the directory is needed)

4. Reboot the machine with the reboot command

5. Replace the product src folder with a newly downloaded copy from Weblutions

6. Reinstall the products npm modules with cd /home/faxstore && npm install (change the directory as needed)

7. Assess if the product remains online once restarted

8. If the above fail, reinstall Node with NVM

Seen Causes of Segmentation Faults

Below is a list of scenarios where this error has occurred and has been resolved.

• Running on Apple devices?
  It's been found on a number of occasions that when running a Weblutions application on a Apple computer (Mac) this error populates. This is due to the encryption method of our products. The error is likely to populate on Mac.

• Server Provider
  In one reported instance the server provider was found to have the incorrecy CPU set in their backend/hypervisor settings which caused the server (VPS) to be attempting to perform actions on an incorrect CPU model in the software compared to the actual CPU in hardware.

This error can be very annoying to diagnose which leads to downtime and a worst experience with our products. If you're experiencing this error on your Weblutions application it's recommended to reach out to us and work with us in regards to solving and diagnosing.