Read the statement by Michael Teeuw here.
"Out of memory" issues - where do I begin?
-
@ember1205 sometimes upgrading one part causes forced upgrades to others and the collection brings more problems…
-
@sdetweil I can appreciate that - I work for a software company, and know about inter-dependencies and the headaches they can cause.
MM is, in a very basic sense, a web server. Electron is a web browser. There shouldn’t be inter-dependencies between a web server and browser, and that seems to be apparent with Chromium not having an issue running against the MM server. So, I would hope that Electron could be brought forward or at least Chromium be documented as an solid alternative.
-
@ember1205 I got us moved from V3 to V6… we need to add another cycle… it didn’t work with V7 last time.
-
@sdetweil v10 is out and listed as “stable”.
-
@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…