[BUG] JavaScript heap out of memory

[Lennys26]

Environment

Self-Hosted (Docker)

System

Docker version 20.10.17

Version

2.1.1

Describe the problem

Installation fails in all cases.

I have attempted:

• docker run -p 8080:80 lissy93/dashy
• docker run -p 8082:80 --name dashy --restart=always --memory=1024m -e NODE_OPTIONS='--max-old-space-size=2048' lissy93/dashy

I have attempted on a Linode VM host with 1 CPU, 1GB RAM with very limited activity, and also on an RPI4, freshly installed/nothing else running.

Additional info

Using TLDR docker run
Using Dashy V-2.1.1. Update Check Complete
✅ Dashy is Up-to-Date

• Building for production...
  WARN A new version of sass-loader is available. Please upgrade for best experience.

<--- Last few GCs --->

[61:0xb4541040] 113142 ms: Scavenge 221.6 (233.2) -> 220.9 (235.5) MB, 6.0 / 0.0 ms (average mu = 0.484, current mu = 0.411) allocation failure
[61:0xb4541040] 114240 ms: Mark-sweep 223.0 (235.7) -> 221.4 (236.2) MB, 1068.7 / 0.1 ms (average mu = 0.349, current mu = 0.133) allocation failure scavenge might not succeed
[61:0xb4541040] 115684 ms: Mark-sweep 223.7 (236.5) -> 222.0 (237.0) MB, 1409.8 / 0.1 ms (average mu = 0.195, current mu = 0.023) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
error Command failed with signal "SIGABRT".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "build-watch" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Using "hacked" docker run:

Using Dashy V-2.1.1. Update Check Complete
✅ Dashy is Up-to-Date

• Building for production...
  WARN A new version of sass-loader is available. Please upgrade for best experience.

<--- Last few GCs --->

[61:0xb45a0040] 116234 ms: Mark-sweep 223.2 (235.6) -> 221.8 (236.1) MB, 1143.6 / 0.1 ms (average mu = 0.243, current mu = 0.021) allocation failure scavenge might not succeed
[61:0xb45a0040] 117683 ms: Mark-sweep 223.8 (236.1) -> 222.4 (236.8) MB, 1422.6 / 0.1 ms (average mu = 0.130, current mu = 0.019) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory`

Please tick the boxes

• You have explained the issue clearly, and included all relevant info
• You are using a supported version of Dashy
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

Yarn

Fast, reliable, and secure dependency management.

[liss-bot]

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

[Lissy93]

Don't forget to check the docs, troubleshooting and other tickets before opening a new issue.

This is covered in the troubleshooting guide in docs, see Troubleshooting Guide → Heap out of Memory.

It's also a duplicate of #380, #350, #297, #349, #510 and #511.

[Lennys26]

The troubleshooting guide (and the related, duplicate cases) indicates to add the --memory=1024m attribute. This was already done.

It appears that was got it to work for me was adding --memory-swap=-1 --memory-swappiness=100.