Mirror turning black after a while

Alvinger

@retroflex I can’t think of anythong off hand.

I am running an older version of MM myself so haven’t researched the electron issues.
Can anyone confirm that the issue started with the new MM version?

As I am running my magic mirror on an original Pi 1 with 256MB RAM with no issues whatsoever I am a bit surprised that the module should cause this.

Edit: MMM-ResRobot has but one dependency and that is the unirest module.

Which version of ResRobot are you running? I did a rewrite to reduce the number of updates w while ago.

cyberdie

@alvinger In my case, the problem started after last MM update.

retroflex

@cyberdie said in Mirror turning black after a while:

@alvinger In my case, the problem started after last MM update.

Same here. Running the latest ResRobot.

But I think others have reported the same problem but with a different module.

Alvinger

@binog @FredJ @cyberdie @schlachtkreuzer6

Looking through the unirest dependencies it looks like it relies on express which may or may not make it sus eptible to the issues with electron.

To resolve this I replaced unirest with node-fetch and pushed the new version of MMM-ResRobot to github.

To upgrade cd to your MagicMirror directory and run the following commands:

git pull
npm remove unirest
npm install

Please post results in this thread!
Hope this resolves the issue.

retroflex

@Alvinger Thanks for the quick fix! :)

My first test…

“top” without ResRobot shows about 1% CPU when idle.
Added ResRobot (old version): “top” shows 100% CPU all the time.
Updated ResRobot, removed unirest, npm install: “top” now shows 1% CPU when idle. Yay!

Looks good so far. Too early to tell anything about memory leaks, but I will keep my mirror running and check tonight. Currently electron shows 18% mem used (for the 2 electron processes).

retroflex

Short lived happiness it seemed… After a few minutes CPU is now back at 100% and memory use increasing. :(

Also tested after reboot of my Pi3 with the same results.

This is my config:

		{
			module: "MMM-ResRobot",
			position: "top_right",
			header: "",
			config: {
				routes: [
					{from: "740015970", to: "740015568"},
				],
				updateInterval: 2 * 60 * 1000,	// Update every second minute.
				maximumEntries: 6,  // Number of departures to show on screen
				truncateAfter: 5,   // A value > 0 will truncate direction name at first space after  characters. 0 = no truncation
				apiKey: "*******"  // Your ResRobot apiKey
			}
		},

Binog

But still, I am not using ResRobot,. and do have the same problem, from time to time,…

Alvinger

@retroflex
I will dig up another respberry pi and try it out. My test environment is a dietpi vm which runs on a pc so I wouldn’t expect the cpu load to be representative of the load on the pi.

FredJ

I also dont think the issue is with ResRobot itself. But it is great that you are looking into it @Alvinger

cyberdie

no ResRobot running on my setup. Think the problem is electron itself.

Alvinger

I agree with others that the problem is most likely related to Electron and not module-specific but rather related to which module dependencies it has.

thejoaovitor

A solution, (not perfect) is to use MMM-WatchDog, it keeps an eye on your UI and quits app in case the UI crashes, combined with the PM2 process manager, MM2 will automaticly restart after a UI failure.

https://github.com/MichMich/MMM-WatchDog

Kuhlemann

The problem still seems to persist also with the newest version of MM. Maybe someone has found a real solution?
I will try out MMM-WatchDog meanwhile.

dazza120

@kuhlemann a cron job is the only way think it seems that it taxes the Pi too much after 8hours or so hence Cron Job every 8hours or so

bachoo786

@dazza120 what are you doing with cron to resolve the issue mate?

dazza120

@bachoo786 hi mate I’ve got a cronjob running at 0400 and 1600 to stop it locking up I’ve just noticed the new one2.7.1 starting to eat the memory as I’ve disabled the cronjob to check out the latest down to 9% after 10hours. So it needs the restarts.

Terminal
Type. Crontab -e
Put times below the line below

m h dom mon dow command

0 4 * * * pm2 reload mm
0 16 * * * pm2 reload mm

Link here https://thepihut.com/blogs/raspberry-pi-tutorials/34930820-running-things-regularly-cron