You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As soon as a peer connection is created via the factory, the Lib uses the default audio inputs.
I write a master->many server, with too many peers Windows terminates the task.
Is there a way to create a peer without input and output sources?
To Reproduce
Steps to reproduce the behavior:
Create some Peer Connections
Sometimes Windows kills the Process with Error (EXCEPTION_ACCESS_VIOLATION (0xc0000005))
Expected behavior
I think Windows is killing the process because too many processes/threads are trying to access the same device.
Screenshots
Desktop (please complete the following information):
OS: Windows 11
Version 22H2 / 22624.1537
The text was updated successfully, but these errors were encountered:
Hello
I have the same issue and i dont create a extra audiooutput just an input with AudioOptions audioOptions = new AudioOptions();
AudioTrackSource audioTrackSource = peerConnectionFactory.createAudioSource(audioOptions);
AudioTrack audioTrack = peerConnectionFactory.createAudioTrack("audio",audioTrackSource);
Error occurs after around 1 minute.
Ok so i found a fix thats working at least for me @Gamer08YT . When i compile it to a jar using maven shade plugin and run it via powershell or cmd the error disappears for me. Currently i have 3 peers connected but just one is sending audio.
Describe the bug
As soon as a peer connection is created via the factory, the Lib uses the default audio inputs.
I write a master->many server, with too many peers Windows terminates the task.
Is there a way to create a peer without input and output sources?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I think Windows is killing the process because too many processes/threads are trying to access the same device.
Screenshots

Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: