MMM-Scenes2

MMRIZE

@Babene1
I researched about that error message.
The error messages seemed not to be the module or logic issue but the GPU/System issue. (Usually in -nix machines about graphic drivers.)

However, I’m not sure the error message is related to your symptom actually. There is a chance these two things could be independent.

What I suggest for the test is;

use simpler animation effects or no animation.
give a longer life for the scene.
Remove all other 3rd party modules, except default modules (clock, …)

If it helps, we can progress from it anyhow.
But if not; I think I rarely have things to do.

Babene1

@MMRIZE

Thank you for your answer, I agree with you, I also think that the error message has nothing to do with the problem.
Error message is written to the log after the start and the freezing of the module happens after about 1 hour.

I used the default animation, unfortunately I don’t know how to remove the animation completely.
Have also removed the MMM remote control module.
So there are only three modules left, MMM-Scenes2, MMM-iFrameReload and MMM-iFrameReload2

I switched off WLan-power Save and deactivated IPV6.

No improvement, no improvement.

Next tests will be longer times and I will use a different browser.

Other test scenarios ?

MMRIZE

@Babene1
To disable animation, you can set animation: null in defaultEnter definition or each scene role definition.

/* example for default behaviour */
defaultEnter: {
  animation: null,
  duration: 1000,
  gap: 0,
},


/* example for each scene definition */
scenario: [
  {
    name: "scene1",
    enter: {
      role: "role1",
      animation: null,
      ...

I’m suspecting Chrome’s memory leaks. These factors may cause memory leaks.

improper handling timer
CSS transition/Animation

I’ll modify some code to confirm to clear out garbage timer. Wait a little.

By the way, can you test the default clock module instead of MMM-iFrame Things? (To make things clearer)

MMRIZE

@Babene1
It’s been updated, but I’m not expecting much. Because timers are rarely used in my code(only two), I don’t think that was the cause of the problem. Anyway, I fixed it so that when the timer is used, it is turned off as soon as possible.

ric

I have switched to MMM-Carousel and experimented with it. It ran for a few days without any problems. Then I installed more modules and customised my configuration. And now the problem is occurring again. The last scene hangs at some point, so I was afraid it might be this one: MMM-BackgroundSlideshow. However, you are not using this, so it is unlikely to be due to this.

My next steps:

disable MMM-BackgroundSlideshow.
completely reinstall everything and only install the modules I want to have at the end and then not change anything else. Let’s see if I will be successful.

MMRIZE

@ric
Chrome(Chromium) is notorious for memory leaks. On Transition/Animation, this kind of error is often reported in some environments (+ some GPU driver issues). Sometimes, a newer version looks like it solves this issue, but the issue returns in subsequent versions again.
If you have more memory, this symptom seems relieving, but not absolutely.

Babene1

Result of my test:

ListenpunktUsing “external_broqwser=firefox” no improvement, after about 1 hour no changes from the modul.
ListenpunktWith “animation: null”, no improvement, after about 1 hour no changes from the modul.
ListenpunktWith default clock and calendar, no problem (test run about 2,5 hours)

Next test, with just an iframe module and the MMM-Simple Logo module. This module combination could be a solution for me

MMRIZE

@Babene1
Do you mean iFrame related module may have the issue?

ric

@MMRIZE
do i understand correctly that the Transition/Animation, could be to blame? So I would have to switch off the transitions for the two modules (MMM-BackgroundSlideshow und MMM-Carousel).
I’ll test it like this

MMRIZE

@ric
Yes, you should try adding one / removing one for all combinations. It would be a very tedious task and requires persistence.