Read the statement by Michael Teeuw here.
Third-Party Module - how to get help?
-
@sdetweil said in Third-Party Module - how to get help?:
https://wpitchoune.net/tricks/raspberry_pi3_increase_swap_size.html
I will give this a shot. Given that each time the slideshow has died, it has indicated that it ran out of memory at roughly 100Mb (and the default swap is 100Mb), this could definitely be related. I’ll try doubling it to see what happens with this module.
I was going to try tackling the transitioning to prevent changing to the new image until it was rendered (to prevent the “painting”), but need the memory issue fixed first. :)
Does your image module contain the JS code you were referring to that hides the image until it’s rendered?
-
@ember1205 yes, it contains the code for the transition handling.
I would make the swap 1 gig… its only a little disk (memory card) space…
the code.
basically it adds an img (appends) to the div to display, the image is hidden,
then there is an onload handler, that gets notified when the image is loaded (not yet visible)
it also adjusts the image size to keep the proportions correct, (css background-size:cover and contain both distort the image)it makes the image visible, and starts the timer for the next image.
it then checks to see if there are TWO images in the div,
if so, it hides the 1st, shows the second and removes the 1st (old image)
repeat -
I will give your code a try. Increasing the swap size and re-enabling the cache resulted in another almost immediate crash.
:(
-
@ember1205 hm… mine runs like a top on pi0 , pi3 b+, pi4, odroid, jetson nano , macOs, ubuntu
my selected pics holds 100 pics, some as large as 15meg. 7.4 meg avg
-
Seems your code has dependencies? I’m getting an error when trying to load:
WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module 'node_helper'
-
@ember1205 node_help is the build in module,
sounds like u did an npm install, even tho not needed (and finds a bug or new feature we don’t want)
recover with this
cd ~/MagicMirror git checkout modules/node_modules/node_helper/index.js
-
@sdetweil said in Third-Party Module - how to get help?:
git checkout modules/node_modules/node_helper/index.js
yeah, I get into the habit of installing add-ons this way and I did the npm install.
Your fix cleaned it right up and it started up. But, guess what? Out of memory again.
Seems that I have bigger issues here…
-
@ember1205 show me the output of
node-v npm -v lsb_release -a uname -a
and other than image, you are running default modules, correct?
I’m gonna be out for a couple hours, running xmas errands. will try to look in on my phone
-
pi@raspberrypi:~ $ node -v v10.17.0
pi@raspberrypi:~ $ npm -v 6.11.3
pi@raspberrypi:~ $ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
pi@raspberrypi:~ $ uname -a Linux raspberrypi 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux
-
@sdetweil said in Third-Party Module - how to get help?:
and other than image, you are running default modules, correct?
I have installed your MMM-ImagesPhotos and MMM-BackgroundSlideshow. Even paring the configuration down to ONLY one third-party module running, it will die unless I have the http cache disabled.
I have changed the swap size from the default of 100 to 250 and when it crashed, there was only a small portion of swap being used.