"Out of memory" issues - where do I begin?

sdetweil

@ember1205 well, the file system loading of the images will be thru the pi, but nothing else…all the display side is done in the browser (which is where it ran out of memory)

ember1205

Well, it isn’t a LOT of progress, but it’s progress.

It’s still crashing. But I managed to get a core dump. And it says that it’s Electron that’s crashing. The initial output from bt has me a little confused as I can’t tell if it didn’t load the symbol file correctly, or if the info just “unknown”. Here’s what I get from a bt command:

Core was generated by `/home/pi/MagicMirror/node_modules/electron/dist/electron --type=renderer --auto'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0  0x02760514 in ?? ()
[Current thread is 1 (LWP 6298)]
(gdb) bt
#0  0x02760514 in ?? ()
#1  0x027603d8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Not really sure if there’s anywhere to go from here. :/

sdetweil

@ember1205 but the other browsers kept going?

i don’t think the symbols are available,certainly not for modules, if that is where the problem is
I would add MMM-Logging (my version) which merges the logs from browser and node_helpers into one log

https://github.com/sdetweil/MMM-Logging

ember1205

Hmmm. Not sure about other browsers since I had shut those down. I’ll wait until it crashes again and see if a secondary browser will keep running.

ember1205

I have confirmed that only Electron crashes on the Pi itself. The MM server does not experience any hiccups and remote browser connections remain functional.

I at least now understand WHAT is crashing. Next steps might be to figure out WHY it’s crashing and potentially remedy it.

sdetweil

@ember1205 note that we are trailing release of electron quite significantly (we are on 6.1.7 and latest is 9.x.x) … you might try moving up to a different version, no guaranty that MM will run tho… or what the other impacts are…

as i said back a few, with a minor startup change, you can get chromium to be the viewer on the pi.

ember1205

I’ve made the change to Chromium - we’ll see how that does going forward.

I do recall reading plenty about the severe lag of Electron in terms of the version that’s part of MM, so that part wasn’t “news” really. What I genuinely don’t understand is why this specific, basic configuration continues to have issues for me while Electron mostly does what it needs to do for so many others without creating this sort of problem.

sdetweil

@ember1205 electron is a ‘single’ threaded app… but events happen that cause it to need to act like mutltiple threads.
there are lots of edge cases where the timing is problematic…

its not out of memory, its lost its way…

i wrote a plugin/module to display pics matches with cal entries, floating above the mirror screen… (pong like moving boxes)
electron does NOT like two windows being manipulated at the same time… took a long time to find that, always an out of memory error or hang… but not

ember1205

Good info.

I’m interested to see how for the MM will make it now using Chromium instead of Electron. Since I have two with the same setup, I’ll set both to use Chromium for an additional level of testing it out.

Why was Electron chosen as the browser up to this point? And, what potential downsides are there to Chromium?

sdetweil

@ember1205 >Why was Electron chosen as the browser up to this point? And, what potential downsides are there to Chromium?

i don’t know and i don’t know… was way before my time.