I installed Node-red using Docker on an ARM architecture Ubuntu system,
I have written a relatively complex Node-red flowchart, and when I use Docker logs to view the logs of Node red, I find that it occasionally encounters Segmentation fault errors:
There are no common reasons as it is a problem that is very rarely seen.
Have a look in syslog and see if there is anything unexpected around the time of the problem.
Is the system performing perfectly in every other way? A hardware problem is one possibility.
Can you post the node red startup log please? Copy/paste, not screenshot.
Also show us what is in your package.json (probably in ~/.node-red, if not there then the startup log will tell you where it is.
12 Jun 00:47:59 - [info] Node-RED version: v3.1.0
12 Jun 00:47:59 - [info] Node.js version: v16.20.2
12 Jun 00:47:59 - [info] Linux 3.10.65-rt69 arm LE
12 Jun 00:48:03 - [info] Loading palette nodes
12 Jun 00:48:15 - [info] Settings file : /data/settings.js
12 Jun 00:48:15 - [info] Context store : 'default' [module=memory]
12 Jun 00:48:15 - [info] User directory : /data
12 Jun 00:48:15 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Jun 00:48:15 - [info] Flows file : /data/flows.json
12 Jun 00:48:15 - [info] Server now running at http://127.0.0.1:1880/
12 Jun 00:48:16 - [warn]
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
12 Jun 00:48:18 - [info] Starting flows
12 Jun 00:48:23 - [info] Started flows
Yes, that is it. It shows what additional nodes you have installed.
Make sure you are using the latest versions of all additional nodes you have installed (use Manage Palette to do that). Also I suggest moving to an up to date version of node red (currently 3.1.10 I think) and a current version of node.js.
By the way, if you surround text such as the log and package.json with lines containing just three backtick characters then that will stop the forum from interpreting them as markdown.
a quick google search would tell you why, but let me do that for you
Joking aside, it is not as easy as you might think. The problem is occuring in some compiled code several layers down (Node-RED code -> NodeJS -> Module -> Sub-Module -> Sub-Module) (I even excluded things like async/callbacks, stack and v8 engine for brevity). We would require a backtrace and then the author of the node (or sub module or sub sub sub x n module) would probably need to analyse the output.