A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
mmap() failed: Cannot allocate memory
-
@Egnos said in mmap() failed: Cannot allocate memory:
Mem: 924 495 54 251 374 127
Swap: 99 99u always have memory available, and never consume any swap space…
-
pi@MagicMirror:~ $ free -m total used free shared buff/cache available Mem: 924 495 54 251 374 127 Swap: 99 99 0
I see that all swap memory is finished … “Used =99 and free=0”.
I dont understand why it is already using swap memory if it is not out of RAM yet …Why the swap memory always occupied?
Finished the task shouldn’t it free itself? -
@Egnos try this
for file in /proc/*/status ; do awk '/VmSwap|Name/{printf $2 " " $3}END{ print ""}' $file; done | sort -k 2 -n -r | less
should give a list of processes using swap, most to least
-
@Egnos so, I would make the swap bigger just for for testing 1 gig
-
@Egnos try this
pm2 stop all export NODE_OPTIONS=--max_old_space_size=4096 npm start
u can add that export line to the installers/mm.sh
if using pm2