Hi, I’m facing an issue with very first step of using libmediasoupclient. When I try to load rtpCapabilities into Device instance then I get std::bad_alloc and stack trace as in screen [image] Do you have any ideas what could be wrong?

Hi, Are you using the exact libwebrtc version indicated in the docs?

yes, m84 - double checked it yesterday. Does --args matters for this? I’ve checked some but not sure what are recommended for Win + VS2019. Are those below ok in your opinion? gn gen out\m84 --args=“is_debug=false is_component_build=false rtc_build_examples=false rtc_include_tests=false rtc_build_s…

There are some args examples in the docs: mediasoup :: Installation Cutting Edge WebRTC Video Conferencing

tried them already…still the same issue

[image] manin: Device instance then I get std::bad_alloc and stack trace as in screen Try inspecting the rtpCapabilities parameter that you pass to the device->Load(rtpCapabilities).

mediasoupclient::Device::load() std::bad_alloc()

mediasoup libraries

peetonn June 25, 2021, 7:25pm 7

@manin have you found a solution? I might be experiencing something similar, not quite sure yet…

Topic		Replies	Views
libmediasoupclient device.Load crashes mediasoup libraries	1	293	September 17, 2023
Crash with "abort signal" when loading device mediasoup libraries	1	214	September 1, 2023
Trace/breakpoint trap in GetNativeRtpCapabilities mediasoup-demo	7	403	May 14, 2023
device.load() throw TypeError mediasoup libraries	6	1134	August 5, 2020
error building mediasoupclient mediasoup libraries	13	748	March 12, 2023

mediasoupclient::Device::load() std::bad_alloc()

Related topics