Read the statement by Michael Teeuw here.
Mirror turning black after a while
-
@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. -
@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).
-
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 } },
-
But still, I am not using ResRobot,. and do have the same problem, from time to time,…
-
@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. -
I also dont think the issue is with ResRobot itself. But it is great that you are looking into it @Alvinger
-
no ResRobot running on my setup. Think the problem is electron itself.
-
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.
-
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.
-
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.