Trixie/node v24 - timeouts on request to the internet

Mr.Sponti

I’ve migrated my MagigMirror installation on a RPI 4 from Bullseye to Trixie, running now MM V2.33.0 and node v24.11.1.
After solving some smaller issues with the NetworkManager configuration, everything is now running fine, except that I observe sometimes timeouts on requests to the internet. Fetching Goggle calendar entries or access to Spotify endpoints sometimes end up in timeouts, particularly visible at startup of MagicMirror. (and no, it’s not related to any wrong URL )

The same MM config is running under Bullseye, MM v2.26.0 and node v20.18.0 without any network issues. It also not a problem of wayland, as I get the same error messages running the config under x11. It seems that this behaviour is related to node V24. Is this a known issue? Is there someone who is fighting with similar issues? Has someone a sustainable solution for that problem?

[2025-12-01 11:52:18.102] [LOG]   Launching application.
[2025-12-01 11:52:22.644] [INFO]
####  System Information  ####
- SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.1; virtual: false; MM: 2.33.0
- OS:       platform: linux; distro: Debian GNU/Linux; release: 13; arch: arm64; kernel: 6.12.47+rpt-rpi-v8
- VERSIONS: electron: 39.2.3; used node: 22.21.1; installed node: 24.11.1; npm: 11.6.2; pm2: 6.0.13
- ENV:      XDG_SESSION_TYPE: tty; MM_CONFIG_FILE: undefined
            WAYLAND_DISPLAY:  wayland-0; DISPLAY: undefined; ELECTRON_ENABLE_GPU: undefined
- RAM:      total: 905.64 MB; free: 397.65 MB; used: 507.99 MB
- OTHERS:   uptime: 23 minutes; timeZone: Europe/Berlin
[2025-12-01 11:52:23.927] [LOG]   Create new calendarfetcher for url: https://calendar.google.com/calendar/ical/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%40group.calendar.google.com/private-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/basic.ics - Interval: 5400000
[2025-12-01 11:52:24.132] [LOG]   Create new calendarfetcher for url: https://www.schulferien.org/media/ical/deutschland/ferien_nordrhein-westfalen_2025.ics?k=wMVRLvKrstqVXYv0MZJF9BwhEW4cGfQFjuutfjiALP5Hj700di6oEuYaFGd4tDTvYrLNzQgB7m-GlFC60I4jasaxLk6nJd_OY70AeBteoOU - Interval: 900000
[2025-12-01 11:52:24.136] [LOG]   Create new calendarfetcher for url: https://calendar.google.com/calendar/ical/de.german%23holiday%40group.v.calendar.google.com/public/basic.ics - Interval: 900000
[2025-12-01 11:52:24.788] [ERROR] Calendar Error. Could not fetch calendar:  https://calendar.google.com/calendar/ical/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%40group.calendar.google.com/private-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/basic.ics TypeError: fetch failed
    at node:internal/deps/undici/undici:14900:13
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at runNextTicks (node:internal/process/task_queues:69:3)
    at process.processTimers (node:internal/timers:520:9) {
  [cause]: AggregateError [ETIMEDOUT]:
      at internalConnectMultiple (node:net:1134:18)
      at internalConnectMultiple (node:net:1210:5)
      at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
      at listOnTimeout (node:internal/timers:590:11)
      at process.processTimers (node:internal/timers:523:7) {
    code: 'ETIMEDOUT',
    [errors]: [ [Error], [Error] ]
  }
}

sdetweil

@Mr.Sponti our code uses a 30 second timeout, but it can be changed by setting an environment variable , here 45 seconds

export mmFetchTimeout=45000
In the script used to launch MagicMirror

See the doc here
https://docs.magicmirror.builders/configuration/introduction.html#advanced-configuration-and-frequently-asked-how-to-configure-examples
I submitted a change to fix the doc which has two defaults specified

But I think you need to fix you network

Mr.Sponti

Hi Sam, thank you for your fast response and support!
I’ve played with the mmFetchTimout parameter without success. As I didn’t had any network issues with Bullseye, MM v2.26.0 and node v20.18.0, I downgraded node to v22.18 and the network issues are gone.
But I’m now faced with another big issue under Trixie. If I schedule modules using graphic functions like vlc, the CPU load increase dramatically. There is one electron process with parameterer –type=zygote consuming the whole CPU capacity.

From copilot I got the answer: High CPU usage from electron --type=zygote is usually tied to Chromium’s zygote process, which forks renderer processes.

Do you have any idea how to get this problem under control?

sdetweil

@Mr.Sponti thanks for the feedback, hadn’t expected node to be the problem .

As for the vlc perf issue , not sure . There have been vlc issues in electron before.

You might try the next release develop branch
See https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

A quick way without touching your existing setup use my backup script to save the module list , config and css
Rename the MagicMirror folder
git clone the repo, checkout the develop branch
Oh it needs node 24 (use n or nvm to switch version)
npm install
Run the restore script to put the modules, config and css in the new MagicMirror folder

https://github.com/sdetweil/MagicMirror-backup-restore