Hey guys, I have some problems with mediasoup. I tried to run project on my local machine while I am creating mediasoup worker it returns me like this error:
Error: [pid:20200, code:3221225477, signal:null]
at ChildProcess.<anonymous> (C:\Users\vonor\OneDrive\mediasoup-sfu-webrtc-video-rooms\node_modules\mediasoup\node\lib\Worker.js:146:43)
at ChildProcess.emit (node:events:518:28)
at ChildProcess._handle.onexit (node:internal/child_process:294:12)
I also tried to run another pc but same error. i don’t know how to fix this error. if you know how to fix this issue please help me.
OS: Windows 11
NODE: v18
Package Manager: YARN@v1.22.22
DEBUG=“mediasoup* ERROR” node server.js
mediasoup createWorker() +0ms
mediasoup:Worker constructor() +0ms
mediasoup:Worker spawning worker process: C:\Users\vonor\OneDrive\test\node_modules\mediasoup\worker\out\Release\mediasoup-worker --logLevel=debug --rt
cMinPort=10000 --rtcMaxPort=59999 +0ms
mediasoup:Channel constructor() +0ms
mediasoup:Channel Producer Channel ended by the worker process +19ms
mediasoup:Channel Consumer Channel ended by the worker process +0ms
mediasoup:ERROR:Worker worker process failed unexpectedly [pid:15684, code:3221225477, signal:null] +0ms
mediasoup:Worker close() +26ms
mediasoup:Channel close() +1ms
I am encountering the same problem and suspect it might be related to the Mediasoup configuration in my project. I deleted the node_modules folder and package-lock.json, then ran npm install and npm rebuild mediasoup to reconfigure the setup. Despite these efforts, the error persists.
I am getting the same error on Windows Server 2022.
Running the same code on Windows Server 2019 and Windows 10 does not produce this error.
Isn’t there anyone else in the community that’s run into this and found a solution?
It’s been reported on Github twice, but because the reporting individual did not provide useful information the bug was closed. How do I go about debugging this in a Windows server environment?
I don’t know about windows but we would accept a PR that adds a more modern version of Windows OS in mediasoup CI actions. That would probably help to see the problem.
Well… for anyone following this, installing node to the server in question fixed the issue. I don’t know what was included by node that mediasoup-worker.exe needed, though.
Before I dig into all the files, do you know of anything specific that node might be including?
I uninstalled node and what I thought was all the dependencies (like Python, and VS 2019 C++ Build Tools) that came with node and restarted the server. However, mediasoup-worker continues to start happily. Which means I still don’t know what the dependency is that mediasoup-worker needed to not have an access violation.
i had same issue what i have done is reinstall the drivers
if they are already in your system u can check from controller panel → programs/features → if it is not here u can install and restart. boom and error gone also check MSVCP140.dll VCRUNTIME140.dll VCRUNTIME140_1.dll as it is available or not in c/system32 directly search in upper right side by name both are present 99% are this error is gone nad no more
I am having the same issue , I have tried installing Microsoft Visual C++ 2015-2022 Redistributable (x64) and that still doesn’t seem to resolve the issue for me.
