[BUG] Waiting for Webserver and high RAM use about companion HOT 18 CLOSED

could you export your config and sent it to me? [email protected]
It launches fine on my windows machine, perhaps it is something specific to certain configs/modules

from companion.

I can but the only module is a Black Magic hyperdeck mini HD.

from companion.

hmm ok. still, it could be something in there that isnt being handled correctly.

I should give the release a try on some other windows machines too , maybe there is something special about mine that makes it work

from companion.

I’m not the only person with the issue. There another report on the slack channel.

from companion.

Same for me, i've tested on many pc also without upgrade but directly the 3.2 version.
the log speak about fonts......
the ram goes full and the machine crash.
the problem is that if i unistall the 3.2 ,to reinstall the old version, alsa the old version don't work.
the temporary solution for me was to install the old version in a clean machine
t

from companion.

thanks for the config, which unsurprisingly did not help to reproduce the issue.
I've tried 3.2 on 4 windows machines now, none of them had any issues with running it.

Could you send the log files? That might have some more info as to what is going wrong. There will be a folder of them at %APPDATA%/companion/logs I think

from companion.

I also have got a Windows 10 LTSC system where this issue occures.

It almost instantly takes gigabytes of RAM but never come up completly.

@Julusian Maybe I can offer you a remote access to the system for further analysis if it would help.

from companion.

2024-01-26T14:16:37.751Z Application: Companion process started
2024-01-26T14:16:40.653Z info Log/Controller Application starting
2024-01-26T14:16:40.660Z info Registry Build 3.2.0+6663-stable-b83f412f
2024-01-26T14:16:40.662Z info Registry configuration directory: C:\Users\Administrator\AppData\Roaming\companion\v3.2
2024-01-26T14:16:40.837Z info Data/Upgrade Upgrading db from version 3 to 4
2024-01-26T14:16:40.865Z info Log/Controller Sentry error reporting configured
2024-01-26T14:16:40.876Z info Graphics/Controller Render worker created
2024-01-26T14:16:40.883Z info Graphics/Controller Render worker created
2024-01-26T14:16:42.771Z Application: Companion looks to be stable
2024-01-26T14:22:19.583Z Application: Companion process started
2024-01-26T14:22:21.877Z info Log/Controller Application starting
2024-01-26T14:22:21.884Z info Registry Build 3.2.0+6663-stable-b83f412f
2024-01-26T14:22:21.885Z info Registry configuration directory: C:\Users\Administrator\AppData\Roaming\companion\v3.2
2024-01-26T14:22:21.975Z info Data/Upgrade Upgrading db from version 3 to 4
2024-01-26T14:22:22.075Z info Log/Controller Sentry error reporting configured
2024-01-26T14:22:22.086Z info Graphics/Controller Render worker created
2024-01-26T14:22:22.092Z info Graphics/Controller Render worker created
2024-01-26T14:22:24.587Z Application: Companion looks to be stable
2024-01-26T14:23:30.268Z Application: Companion process started
2024-01-26T14:23:31.894Z info Log/Controller Application starting
2024-01-26T14:23:31.899Z info Registry Build 3.2.0+6663-stable-b83f412f
2024-01-26T14:23:31.900Z info Registry configuration directory: C:\Users\Administrator\AppData\Roaming\companion\v3.2
2024-01-26T14:23:31.989Z info Data/Upgrade Upgrading db from version 3 to 4
2024-01-26T14:23:32.029Z info Log/Controller Sentry error reporting configured
2024-01-26T14:23:32.044Z info Graphics/Controller Render worker created
2024-01-26T14:23:32.053Z info Graphics/Controller Render worker created
2024-01-26T14:23:35.267Z Application: Companion looks to be stable
2024-01-26T14:24:25.174Z Application: Restart Count: 1
2024-01-26T14:24:27.965Z info Log/Controller Application starting
2024-01-26T14:24:27.970Z info Registry Build 3.2.0+6663-stable-b83f412f
2024-01-26T14:24:27.971Z info Registry configuration directory: C:\Users\Administrator\AppData\Roaming\companion\v3.2
2024-01-26T14:24:28.046Z info Data/Upgrade Upgrading db from version 3 to 4
2024-01-26T14:24:28.069Z info Log/Controller Sentry error reporting configured
2024-01-26T14:24:28.078Z info Graphics/Controller Render worker created
2024-01-26T14:24:28.083Z info Graphics/Controller Render worker created
2024-01-26T14:24:31.272Z Application: Companion looks to be stable
2024-01-26T14:25:21.368Z Application: Companion process started
2024-01-26T14:25:23.470Z info Log/Controller Application starting
2024-01-26T14:25:23.478Z info Registry Build 3.2.0+6663-stable-b83f412f
2024-01-26T14:25:23.480Z info Registry configuration directory: C:\Users\Administrator\AppData\Roaming\companion\v3.2
2024-01-26T14:25:23.601Z info Data/Upgrade Upgrading db from version 3 to 4
2024-01-26T14:25:23.642Z info Log/Controller Sentry error reporting configured
2024-01-26T14:25:23.657Z info Graphics/Controller Render worker created
2024-01-26T14:25:23.666Z info Graphics/Controller Render worker created
2024-01-26T14:25:26.367Z Application: Companion looks to be stable

from companion.

from companion.

after that the ram became full and the system crash

from companion.

after using "REVO uninstaller" I managed to install the old "companion-win64-3.0.0+6000-beta-52f8eec5" and it works perfectly

from companion.

also the v3.1.2 2023-11-01 is running

from companion.

hmm that log is interesting as it appears that companion is getting stuck in a restart loop, but I couldn't say why that is happening from those logs, or why it results in such an agressive memory leak.

@premultiply yeah that would be really helpful. please email me or message me on slack to arrange this.

from companion.

Having the same issue on one machine

from companion.

I think I have a 'fix' for this, a beta build with the fix applied is building now, once it has the website will offer a 6710 beta build.
I shall do a 3.2.1 release later today or tomorrow with this fix.

It would be useful to understand why this happened. Could people with this issue provide some details about the machine:

• Windows version (eg 10 1809 LTSC)
• CPU model
• GPU model

maybe there is something in common which would help narrow down why this font was causing an issue

from companion.

I would like to try the fix in 3.2.1 but there doesn't seem to be a docker image for it yet.

from companion.

v3.2.1 is released with the fix for this.

I don't have enough data to confirm any commonality in systems, so I can't be sure it will work in every case, and I havent been able to try setting up a machine the same as the one case I know of

from companion.

I was able to fix the issue by setting up http port to 8000 instead of 8484. I believe the default port changed in an update.

from companion.