@Babene1
Congrat. Happy to hear that. (Mine is not guilty! :D)

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

@Como
Can you share me your ics file/url and your config with me(eouia0819@gmail.com)

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

@dpnguyen
You may need update your electron/chromium to the recent version. Your Chrome/Chromium might be a quite old. (before 2023 Feb.)

I mean, you need to update MagicMirror to recent version, not Chromium on your RPI or OS.

@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.

@sdetweil
I prefer bash. For similar experience with real -NIX/MacOS.

@JohnGalt
To be honest, I always install MM on various env, manually by myself. Never with his script. So my experience will not be helpful.
Anyway,
Even in windows (I installed MM many times on Windows) it is always same.

1. Install git-bash
2. Install nvm-for-windows, then install node js through it.
3. Make a working directory for MM on git-bash terminal.
4. Clone repository of MM on that directory with git command.
5. Edit some path in package.json for Windows.
6. execute npm install.
7. Make config.js, custom.css
8. For fonts and bundle, install them.

Well, For me it’s not difficult at all but I recommend @sdetweil ‘s script for beginners. As far as I know, it will work on all Windows version.

@plainbroke can you install MM on your windows and be able to run it? Or should we start from there?

@plainbroke which environment are you using?

@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.

@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)

@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.

Anyway, I stopped to maintain CX2.
You can use MMM-CalendarExt3Agenda instead. It could have similar looks, though not identical.

@veny
I tested but nothing special wrong.

This is my config for my Google Calendar ics.

{
  module: 'MMM-CalendarExt2',
  config: {
    calendars : [
      {
        url: "https://calendar.google.com/calendar/ical/4b9c...6390%40group.calendar.google.com/private-e481c...c7cc/basic.ics",
			},
		],
		scenes: [
			{
				name: "DEFAULT",
			},
		],
		views: [
			{
				mode: "daily",
				name: "DAILY_VIEW",
			}
		],
  },
},

I used Secret address URL for ical format, you looks also use that URL too.

[2024-05-18 13:27:05.414] [LOG]   [CALEXT2] calendar:0 >> Scanned: 1, Selected: 1 

Your log says the parsing completed successfully for your ics. It may have 1 event.

However, I have no idea why the module doesn’t appear. Maybe other module may interrupt something.
To make things simple, you can test a new config without other modules except MMM-CalendarExt2 and clock module. You can focus the issue only.

@veny
That error log doesn’t help. No idea.

Just for confirmation about still-working. (2024-05-16)

Both electronOptions and electronSwitches to be added must reside within the config variable in config.js. I didn’t mention it because it seemed obvious. Surprisingly, it seems to be misunderstood as adding this to the end of the file.

I tested on my Mac, it works still.(MM 2.27) For linux, I believe it has to work also. (Because it is one of the default features of the Electron.)

CONFIG.JS

/* config.js */
...
timeFormat: 24,
units: "metric",

/* Insert here */
electronOptions: {
	fullscreen:  false,
	backgroundColor: '#00000000',
	titleBarStyle: 'none',
	frame: false,
	type: 'desktop',
	hasShadow: false,
	transparent: true,
	resizable:   false,
},
electronSwitches: ["enable-transparent-visuals"],

modules: [
	{
		module: "clock",
		position: "top_left"
	},
...

CUSTOM.CSS

/* custom.css */
:root {
  --color-text: #ddd;
  --color-text-dimmed: #bbb;
  --color-text-bright: #fff;
  --color-background: rgba(0, 0, 0, 0);
  /* make fonts color brighter */

  --font-size: 2vh;
  --font-size-small: 0.75rem;

  --gap-body-top: 20px;
  --gap-body-right: 120px;
  --gap-body-bottom: 20px;
  --gap-body-left: 40px;
  /* adjust margin for your screen */
}

* {
  text-shadow: 2px 2px 5px #000000; /* make text more readable on the background image */
}

@LoneSoldier
On which lines did you put the additional configurations? Last line? Show me full config.js.

@sdetweil
For Linux, there are many distros, so I’m not sure it works on all environments.
For Mac/Windows, I think it will still work.