# mediasoupclient::Device::load() std::bad\_alloc()

**URL:** <https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854>\
**Category:** mediasoup libraries\
**Created:** [May 31, 2021, 12:08pm UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854 "2021-05-31T12:08:56Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![manin](https://avatars.discourse-cdn.com/v4/letter/m/bc79bd/32.png) [@manin](https://mediasoup.discourse.group/u/manin)\
**Post date:** [May 31, 2021, 12:08pm UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854/1 "2021-05-31T12:08:56Z")

</div>

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](https://global.discourse-cdn.com/free1/uploads/mediasoup/original/2X/f/f298e978063f33a80df3f79f5bb2b9ea85105735.png)  
Do you have any ideas what could be wrong?

---

<div class="post-metadata">

**Author:** ![jmillan](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/jmillan/32/9_2.png) [@jmillan](https://mediasoup.discourse.group/u/jmillan)\
**Post date:** [June 1, 2021, 8:26am UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854/2 "2021-06-01T08:26:12Z")

</div>

Hi,

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

---

<div class="post-metadata">

**Author:** ![manin](https://avatars.discourse-cdn.com/v4/letter/m/bc79bd/32.png) [@manin](https://mediasoup.discourse.group/u/manin)\
**Post date:** [June 2, 2021, 8:30am UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854/3 "2021-06-02T08:30:31Z")

</div>

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\_ssl=false rtc\_ssl\_root=“C:\Program Files (x86)\OpenSSL\include” use\_rtti=false use\_custom\_libcxx=false treat\_warnings\_as\_errors=false is\_clang=false”

---

<div class="post-metadata">

**Author:** ![jmillan](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/jmillan/32/9_2.png) [@jmillan](https://mediasoup.discourse.group/u/jmillan)\
**Post date:** [June 2, 2021, 12:03pm UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854/4 "2021-06-02T12:03:24Z")

</div>

There are some args examples in the docs:

> **[mediasoup :: Installation](https://mediasoup.org/documentation/v3/libmediasoupclient/installation/)**
>
> Cutting Edge WebRTC Video Conferencing

---

<div class="post-metadata">

**Author:** ![manin](https://avatars.discourse-cdn.com/v4/letter/m/bc79bd/32.png) [@manin](https://mediasoup.discourse.group/u/manin)\
**Post date:** [June 2, 2021, 12:36pm UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854/5 "2021-06-02T12:36:38Z")

</div>

tried them already…still the same issue

---

<div class="post-metadata">

**Author:** ![copiltembel](https://avatars.discourse-cdn.com/v4/letter/c/e9a140/32.png) [@copiltembel](https://mediasoup.discourse.group/u/copiltembel)\
**Post date:** [June 2, 2021, 5:47pm UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854/6 "2021-06-02T17:47:33Z")

</div>

> [@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)`.

---

<div class="post-metadata">

**Author:** ![peetonn](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/peetonn/32/923_2.png) [@peetonn](https://mediasoup.discourse.group/u/peetonn)\
**Post date:** [June 25, 2021, 7:25pm UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854/7 "2021-06-25T19:25:33Z")

</div>

@manin have you found a solution? I might be experiencing [something similar](https://mediasoup.discourse.group/t/all-places-when-peer-connection-factory-is-created/2965), not quite sure yet…

---

<div class="post-metadata">

**Author:** ![manin](https://avatars.discourse-cdn.com/v4/letter/m/bc79bd/32.png) [@manin](https://mediasoup.discourse.group/u/manin)\
**Post date:** [June 28, 2021, 6:03am UTC](https://mediasoup.discourse.group/t/mediasoupclient-load-std-bad-alloc/2854/8 "2021-06-28T06:03:26Z")

</div>

not yet ☹
