[BUG] Companion 3.4.2 Crash "Houston, We have a problem"

[MixAnalogue]

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

At the time of the error I was attempting to load the Companion web gui. There was a single module that was in error state (CR3_IPTV). It was loading the connections page when "Houston, We have a problem" appeared. After a few seconds the web gui loaded and the modules became connected. All attached surfaces via satellite were disconnected at this time.

Below is the copied log from when the error occurred.

Companion Crash 2024-10-15.txt

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

• OS: Windows 10
• Browser: Chrome Version 128.0.6613.138
• Companion Version: 3.4.2 Stable

Additional context

No response

[Julusian]

I want to partly blame the module for this. That log file contains 5 log lines before companion crashed with being out of memory.
Each of those 5 log lines is 440000 bytes long, and were received 13ms apart.
So if that was happening for a while, it is logging at about 33MB/s, which is a lot. After 60s, that is 2GB of logs.

Maybe Companion can be doing more to avoid this crash, but also the module should not be logging that much. That logging is not going to be useful to anyone.

[JuddiP]

Thanks for your input @Julusian -- module dev will take a look at the logging issue for this module (and a few others recently developed) when time allows.