MM startup problem after update

manu85340

@sdetweil I have an error see below, thanks Sam

pi@MagicMirror:~/MagicMirror $ git checkout -b temp v2.27.0
Basculement sur la nouvelle branche ‘temp’
pi@MagicMirror:~/MagicMirror $ rm package-lock.json
pi@MagicMirror:~/MagicMirror $ rm -rf node_modules
pi@MagicMirror:~/MagicMirror $ npm run install-mm

magicmirror@2.27.0 install-mm
npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev

/
<— Last few GCs —>

[25028:0x4545870] 27358 ms: Mark-sweep (reduce) 226.0 (233.8) -> 225.8 (233.8) MB, 271.2 / 0.0 ms (average mu = 0.812, current mu = 0.296) allocation failure; scavenge might not succeed
[25028:0x4545870] 27592 ms: Mark-sweep (reduce) 226.3 (233.8) -> 226.2 (234.3) MB, 230.3 / 0.0 ms (average mu = 0.653, current mu = 0.018) allocation failure; scavenge might not succeed

<— JS stacktrace —>

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
Aborted
pi@MagicMirror:~/MagicMirror $

BKeyport

You know, I just realized that the “blank screen” I mentioned earlier was actually just my screen setup. In fact, this is the same errors I was having with the NPM/Node being out of date…

manu85340

@BKeyport ok thank you for your answer I’m waiting to see if @sdetweil sdetweil finds a solution

sdetweil

@manu85340 see this post (and the one before it) in an issue w the same problem
https://github.com/sdetweil/MagicMirror_scripts/issues/89#issuecomment-2176865685

manu85340

@sdetweil hi Sam if I understand correctly it is not possible to restart the MM with the update that I passed, that’s it,

sdetweil

@manu85340 I don’t understand.

we have restored back to 2.27

2.28 will not run on buster

you need the next at least bullseye
bur if you are upgrading, go to current, bookworm

manu85340

@sdetweil Sam a few posts above I told you that I had a problem passing this line:

git checkout -b temp v.2.27.0

so I didn't pass the other command lines

rm package-lock.json
rm -rf node_modules
npm run install-mm

sdetweil

@manu85340 yes and I replied with the corrected command
https://forum.magicmirror.builders/topic/18838/mm-startup-problem-after-update/30?_=1719933486042

manu85340

@sdetweil Yes, that’s true, sorry, but then I made another comment to let you know that I had an error when I passed the line: ```
npm run install-mm

pi@MagicMirror:~/MagicMirror $ npm run install-mm

magicmirror@2.27.0 install-mm
npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev

/
<— Last few GCs —>

[12543:0x5273870] 17046 ms: Mark-sweep (reduce) 226.7 (234.0) -> 226.5 (234.0 ) MB, 147.4 / 0.0 ms (+ 65.0 ms in 7 steps since start of marking, biggest step 17.7 ms, walltime since start of marking 223 ms) (average mu = 0.854, current m u = 0.346) allo[12543:0x5273870] 17258 ms: Mark-sweep (reduce) 226.9 (234.0) -> 226.9 (234.5) MB, 207.1 / 0.0 ms (average mu = 0.705, current mu = 0.026) al location failure; scavenge might not succeed

<— JS stacktrace —>

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memor y
Aborted

sdetweil

@manu85340 and then i posted another link with instructions for that problem