Read the statement by Michael Teeuw here.
"Out of memory" issues - where do I begin?
-
@ember1205 hm… do this
cd ~/MagicMirror ./run-start.shyou should see something like this
./run-start.sh [2020-09-22 13:13:51.584] [LOG] Starting MagicMirror: v2.13.0-develop [2020-09-22 13:13:51.588] [LOG] Loading config ... [2020-09-22 13:13:51.590] [LOG] Loading module helpers ... [2020-09-22 13:13:51.590] [LOG] No helper found for module: alert. [2020-09-22 13:13:51.602] [LOG] Initializing new module helper ... [2020-09-22 13:13:51.602] [LOG] Module helper loaded: updatenotification [2020-09-22 13:13:51.603] [LOG] No helper found for module: clock. [2020-09-22 13:13:51.840] [LOG] Initializing new module helper ... [2020-09-22 13:13:51.840] [LOG] Module helper loaded: calendar [2020-09-22 13:13:51.841] [LOG] No helper found for module: compliments. [2020-09-22 13:13:51.841] [LOG] No helper found for module: currentweather. [2020-09-22 13:13:51.841] [LOG] No helper found for module: weatherforecast. [2020-09-22 13:13:52.147] [LOG] Initializing new module helper ... [2020-09-22 13:13:52.147] [LOG] Check MagicMirror version for node helper 'MMM-Ring' - Minimum version: 2.11.0 - Current version: 2.13.0-develop [2020-09-22 13:13:52.147] [LOG] Version is ok! [2020-09-22 13:13:52.148] [LOG] Module helper loaded: MMM-Ring [2020-09-22 13:13:52.148] [LOG] All module helpers loaded. [2020-09-22 13:13:52.186] [LOG] Starting server on port 8090 ... [2020-09-22 13:13:52.187] [INFO] You're using a full whitelist configuration to allow for all IPs [2020-09-22 13:13:52.190] [LOG] Server started ... [2020-09-22 13:13:52.190] [LOG] Connecting socket for: updatenotification [2020-09-22 13:13:52.190] [LOG] Connecting socket for: calendar [2020-09-22 13:13:52.190] [LOG] Starting node helper for: calendar [2020-09-22 13:13:52.191] [LOG] Connecting socket for: MMM-Ring [2020-09-22 13:13:52.196] [LOG] MMM-Ring at (9/22/2020, 1:13:52 PM): Starting module: MMM-Ring [2020-09-22 13:13:52.196] [LOG] Sockets connected & modules started ... [2020-09-22 13:13:52.196] [LOG] Ready to go! Please point your browser to: http://0.0.0.0:8090 Starting chromium browser now, have patience, it takes a minutethat last line is the key to running in split mode, server with chromium over the top…
to run it multiple times, you will have to kill the server process
ps -ef | grep serversam 3267 3266 1 13:13 pts/0 00:00:01 node serveronly
kill -9 3267thx for the hint, the space after the serverOnly:
-
@ember1205 I just updated the script to handle with/without the space…
-
Cool. I download the latest one and try it out.
Glad I can help you keep improving your code! lol
-
@ember1205 said in "Out of memory" issues - where do I begin?:
Glad I can help you keep improving your code! lol
me too… thought I had handled that… guess not
-
Based on the directions you gave in this thread, the run-start.sh script won’t work. I didn’t take the time to look through the github content to see if this is covered there, but you have to do
chmod +x run-start.shOr the script won’t actually execute. Based on old habits, I was executing the chmod statement without even thinking about it. But, after downloading the newest script, I purposefully left it untouched and it wouldn’t run.
-
@ember1205 hm, thought it was uploaded with exec. will check this evening. have doctor appt shortly
thanks for the info
-
I simply opened the github page, copied the link, and used wget to download it to the mirror. So, it’s entirely possible that the way I downloaded it was partly to blame. Figured I would mention it because I’m likely not the only one that might run into this, and at a minimum it could become a troubleshooting step if others run into issues.
-
@ember1205 thx. wget & curl won’t copy the execute permissions. when I install this on a pi 0 I chmod it to executable
-
You can’t make this stuff up…
Mirror has been running for a couple of hours now without crashing as it has been doing intermittently in the past. However, there is now a “pop up” on the screen stating that Chromium couldn’t be updated and that I’m missing out on features and fixes.
I found what might be a fix in the way of potentially “configuring” Chromium to ignore updates, but I won’t know if this truly works until probably tomorrow at the earliest.
-
I’m now about 2.5 days into two MM’s running without crashes using Chromium instead of Electron. I’ve also not seen a return of the pop up from Chromium about needing to be updated.
For those that might need to correct the update issue, here’ s what I did on my mirrors:
sudo touch /etc/chromium-browser/customizations/01-disable-update-check;echo CHROMIUM_FLAGS=\"\$\{CHROMIUM_FLAGS\} --check-for-update-interval=31536000\" | sudo tee /etc/chromium-browser/customizations/01-disable-update-check
