Read the statement by Michael Teeuw here.
"Out of memory" issues - where do I begin?
-
@ember1205 yeh, that and a quarter!!.. V7 was stable when we tried it last year too… running on PI is a whole different thing… they test on x86.
-
Update… 30 full days since my last post about stability and have not experienced a single crash on either mirror. So, Electron is definitely the source of the problem.
Thank you to @sdetweil for the assistance in swapping over to Chromium and getting things to a stable state.
-
@ember1205 thank you for the feedback… there is a proposal to move to Electron V10
-
Wanted to post what is likely a ‘final update’ to this thread. I was running for literally weeks if not months with zero issues. I even let the system run for at least a month with the “you’re out of date” banner across the top and not one crash.
I updated the mirror and it reverted itself back to using Electron (that in itself is infuriating) and it’s crashing again. So, not only is Electron the problem but it’s STILL a problem.
I’ve reverted my mirror back to the outdated code and will do another update and not allow it to change back to Electron so that it can run without crashing!
-
@ember1205 what do you mean ‘updated’? if u just did a git pull, then u updated to the same level of electron
new release coming this week (1/1) which moves up to electron 8. 5.3
if u want to test it today, use the develop branch
both still use only electron, you can reinsert run-start.sh to use chromium
-
@sdetweil I used your upgrade script on my mirror. During the upgrade, it reverted the configuration back to using Electron instead of retaining the run-start.sh directive that would launch Chromium.
I wiped out the entire MM directory and copied back the working one that wasn’t upgraded. Unfortunately, it now seems that it is refusing to run the upgrade script and I’m wondering if it’s a certificate issue and I need to update the Pi itself first…
-
@ember1205 the upgrade doesn’t know about your local change to use run-start… but all u had to do was restore that one line in package.json
it now seems that it is refusing to run the upgrade script
show me the ~/MagicMirror/installers/upgrade.log
-
@sdetweil This is all that it spits out on a test run (and MM no longer shows that it is out of date but it is):
Upgrade started - Mon Dec 28 09:07:08 EST 2020 system is Linux raspberrypi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster doing test run = true, NO updates will be applied! saving custom.css Unable to determine upstream git repository restoring custom.css removing git alias Upgrade ended - Mon Dec 28 09:07:09 EST 2020I tried connecting to a couple of web sites via CURL and it throws errors about loading certificates and these sites should work fine. So, the combo of everything is why I’m suspecting that there is a certificate issue due to an older OS on the Pi. I’m doing an upgrade on it now…
-
@ember1205 when u made your backup, how did u do it? you may not have backed up the git repo
from the MagicMirror folder
do a git status
and ls .git (notice the leading dot) -
@sdetweil I honestly don’t recall if I renamed the original folder MM-backup/ and then did rsync back to MagicMirror/ or just did rsync to MM-backup/. My rsync would have been with flags ‘-vaPHSx’, so either way it should have gotten everything.
I’ll check for the .git directory…
