Black Screen Of Death After Couple of Hours

[dazza120]

Hi, as per the description, my magic mirror seems to go black screen after about 6 or so hours the first time i done the magic mirror on the Pi 3B+ the SD corrupted its a Sand disk 32Gb extreme, Pi is connected via ethernet and connection via VNC server. Im a Noob so be gentle :) ive looked every where for a solution other than starting a cronjob every 6 hours which is a pain as ive installed MMM-voice and want to control it through that but cronjob pm2 restart mm, loads everything afresh again meaning you have to change it to voice mode and all modules are displayed.

List of Modules MMM-NetworkConnection, default cal to UK, clock,weather forecast, current weather all default ones, updatenotification has been deleted from config.js. MMM-GoogleMapsTraffic, MMM-Hue and MMM-SystemStatus. So the magic mirror screen has gone black and its still open just alt-m and im connected via VNC and typing this on my iphone via the Pi so im actually doing this through the pi with 5chromium pages open and terminal so the pi itself hasn’t crashed. Ill post a log to the crash hopefully someone can help me out but seems that the black screen of death is not a new thing but still cant find a solution to it. thanks in advance for your help.

pm2 log mm
[TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option)
/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm | at loadConfig (/home/pi/MagicMirror/js/app.js:77:4)
0|mm | at App.start (/home/pi/MagicMirror/js/app.js:206:3)
0|mm | at Object. (/home/pi/MagicMirror/js/electron.js:116:7)
0|mm | TypeError: Cannot read property ‘split’ of undefined
0|mm | at loadModule (/home/pi/MagicMirror/js/app.js:108:25)
0|mm | at loadNextModule (/home/pi/MagicMirror/js/app.js:161:5)
0|mm | at /home/pi/MagicMirror/js/app.js:163:6
0|mm | at loadModule (/home/pi/MagicMirror/js/app.js:146:4)
0|mm | at loadNextModule (/home/pi/MagicMirror/js/app.js:161:5)
0|mm | at loadModules (/home/pi/MagicMirror/js/app.js:172:3)
0|mm | at /home/pi/MagicMirror/js/app.js:218:4
0|mm | at loadConfig (/home/pi/MagicMirror/js/app.js:77:4)
0|mm | at App.start (/home/pi/MagicMirror/js/app.js:206:3)
0|mm | at Object. (/home/pi/MagicMirror/js/electron.js:116:7)
0|mm | [32402:1208/231022.758399:FATAL:bus.cc(1152)] D-Bus connection was disconnected. Aborting.

/home/pi/.pm2/logs/mm-out.log last 15 lines:
0|mm | Connecting socket for: MMM-NetworkConnection
0|mm | MMM-NetworkConnection helper started …
0|mm | Connecting socket for: MMM-GoogleMapsTraffic
0|mm | Starting node_helper for module: MMM-GoogleMapsTraffic
0|mm | Connecting socket for: MMM-SystemStats
0|mm | Connecting socket for: newsfeed
0|mm | Starting module: newsfeed
0|mm | Sockets connected & modules started …
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://www.officeholidays.com/ics/ics_country_code.php?iso=GB - Interval: 4000000
0|mm | Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-GET payload: { style: ‘standard’ }
0|mm | Create new news fetcher for url: http://feeds.bbci.co.uk/news/uk/rss.xml - Interval: 300000
0|mm | MMM-voice: Checking files.
0|mm | starting network connection testing
0|mm | MMM-voice: Starting pocketsphinx.

0|mm | Whoops! There was an uncaught exception…
0|mm | MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|mm | If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
0|mm | { Error: spawn ENOMEM
0|mm | at _errnoException (util.js:1024:11)
0|mm | at ChildProcess.spawn (internal/child_process.js:323:11)
0|mm | at exports.spawn (child_process.js:514:9)
0|mm | at Object.exports.execFile (child_process.js:224:15)
0|mm | at Object.module.(anonymous function) [as execFile] (ELECTRON_ASAR.js:199:20)
0|mm | at exports.exec (child_process.js:154:18)
0|mm | at childProcess.(anonymous function) (ELECTRON_ASAR.js:689:22)
0|mm | at /home/pi/MagicMirror/modules/MMM-SystemStats/node_modules/async/dist/async.js:66:19
0|mm | at /home/pi/MagicMirror/modules/MMM-SystemStats/node_modules/async/dist/async.js:3880:24
0|mm | at eachOfArrayLike (/home/pi/MagicMirror/modules/MMM-SystemStats/node_modules/async/dist/async.js:1069:9) code: ‘ENOMEM’, errno: ‘ENOMEM’, syscall: ‘spawn’ }

[sdetweil]

@dazza120 said in Black Screen Of Death After Couple of Hours:

0|mm | { Error: spawn ENOMEM

means no memory available to lauch the background app…

usually means doing more than physical memory can handle…

so… see https://www.answiz.com/questions/22232/node-js-catch-enomem-error-thrown-after-spawn
to verify no swap and enable it

mmm-voice…
YOU don’t have to change to voice mode… just speak and IT will change the first time… (least thats what happens for me)

[dazza120]

Thanks that’s a bummer :( i’ll Try changing the update intervals for GoogleMapsTraffic as that’s what it could be, thanks for your help

[Klinge]

Hello,

I have the same problem with the black screen and google maps.

Have you already found a solution?

Thank you.
Lars

[dazza120]

@Klinge only to do a Cron Job on the Pi every12hours

[CyruS1337]

@dazza120 @Klinge Unfortunately, I have to do so, have currently found no other solution.

[Fonfon]

@dazza120 said in Black Screen Of Death After Couple of Hours:

only to do a Cron Job on the Pi every12hours

Hi,
I Have The same issue with google traffic, black srceen after 2 days.

<thanks for your help

[MadScientist]

@fonfon which module are you using? AFAIK @sdetweil created a modified version to stop the memory issue. At least that’s what I vaguely remember.

I am sure he’ll pass by within minutes to either confirm or deny :beaming_face_with_smiling_eyes:

[Fonfon]

@sdetweil , ok thanks @MadScientist i find the modified module
how i can change mine only on change this file “MMM-GoogleMapsTraffic.js”

Thanks !

[MadScientist]

@fonfon The way I would do it:
Rename the old folder of the old Maps-Module and download the new, modified version. Enter the folder of the new version and run npm install. Config should be the same, so no need to change anything there.

Test and report back if everything worked.