[BUG] particular VMIX preset makes companion segfault

[BarbeRousseDeVicto]

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

I have my VMIX loaded from a saved PRESET that seem to make companion crash randomly, it didn't happen with any other PRESET.
The issue is I can't see anywhere in the LOG what cause the issue.

So Randomly companion reset his config, like is I have some button in step 2, they will came back to step 1, like if I have close and reopen the companion app, but the companion app stay open, it only read the config and apply the layout.

In the webpage I get the "Houston we have problem" splash screen then 1-2 seconds later it came back to life itself.

There is nothing in VMIX log (vmix didn't crash at all) there is nothing in the Windows Event manager, and the Companion LOG reset like when it was turn on for the first time.

TVCBF-REGIE_2025-02-11-2302_companion-config.zip

Steps To Reproduce

This happen randomly, I can try all the button I have config for this VMIX PRESET but nothing will make it crash for sure. it happen randomly even if I didn't touch the computer.

Expected Behavior

No response

Environment (please complete the following information)

- OS: Windows 11
- Browser: Chrome 111
- Companion Version: v4.0.0+7836-main-88a6a1d0   but happen on the 3.4.3, 3.5.1 too

Additional context

I have attatch my log debug files if anyone can find where my issue could be.

Redo the VMIX PRESET isn't really something i want to do since there is a lot of configuration inside this TV SHOW

[BarbeRousseDeVicto]

Yes i do with the 3.4.3 and the 3.5.1 too, same result this is why I have try the v4 to see if there is any fix ***@***.*** De : Jeff Martin ***@***.***> Envoyé : 12 février 2025 14:48 À : bitfocus/companion ***@***.***> Cc : Nicolas Simoneau ***@***.***>; Author ***@***.***> Objet : Re: [bitfocus/companion] [BUG] particular VMIX preset seem to make companion "reset" (Issue #3282) Vous n'obtenez pas souvent d'e-mail à partir de ***@***.******@***.***>. Pourquoi c'est important<https://aka.ms/LearnAboutSenderIdentification> Have you tried using the Stable release? The v4.0.0 Beta is very new and has a lot of bugs so isn't intended for production use yet. - Reply to this email directly, view it on GitHub<#3282 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCXQSESSRO4M3X3FEV4OW7T2POQO3AVCNFSM6AAAAABXAHYYJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJUGY4TKMBZGQ>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[thedist]

Looking at that exit code, and the errors you are getting, it doesn't appear to be vMix related, especially as modules themselves are isolated from Companion and run in their own processes and it's the Companion process that is cause a segfault not the vMix module.

Edit: The only vMix errors I'm seeing so far are related to invalid variables, which looks like it could be an encoding issue (are you using any non-ASCII symbols in your vMix production at all, like symbols, emoji, or anything like that?) but I don't believe that should cause an issue with Companion itself.

[Julusian]

Yeah that looks to be a nasty crash. Unfortunately the log isn't indicating where it happened, so this isn't going to be trivial to diagnose..

[BarbeRousseDeVicto]

I have this in my log now with V4

2025-02-18T23:36:59.437Z Application: Companion exited with code: 3221225477
2025-02-18T23:36:59.437Z Application: Restart Count: 1

What is this code related to ???

companion-2025-02-18.0.log

[BarbeRousseDeVicto]

This morning with a fresh windows format and reinstall I still have: Companion exited with code: 3221225477

So this seem related to my VMIX profile 100% sure now. Or maybe some python automation I have here.

If anyone can help me to understard error 3221225477 it will be apreciated

[BarbeRousseDeVicto]

After some search it seem related to the NODE.exe process new in V3

SegfaultHandler: The exception won't be logged into a file, unless 'segfault.log' exists.

PID
8720 received ACCESS_VIOLATION for address: 0x7ff7f60e6998
[node-napi-v9.node]: segfault::init
[node-napi-v9.node]: segfault::showCallstack
[node-napi-v9.node]: segfault::handleSignal
[KERNELBASE.dll]: UnhandledExceptionFilter
[ntdll.dll]: memset
[ntdll.dll]: _C_specific_handler
[ntdll.dll]: _chkstk
[ntdll.dll]: RtlRaiseException
[ntdll.dll]: KiUserExceptionDispatcher
[node.exe]: v8::base::MagicNumbersForDivision::operator==
[node.exe]: v8::Object::GetIsolate
[node.exe]: v8::Object::GetIsolate
[node.exe]: v8::Object::GetIsolate
[node.exe]: v8::SharedValueConveyor::SharedValueConveyor
[node.exe]: v8::SharedValueConveyor::SharedValueConveyor
2025-02-20T14:29:29.306Z Application: Companion exited with code: 3221225477