# Metadata buffer for crash for Android

**URL:** <https://devforum.zoom.us/t/metadata-buffer-for-crash-for-android/125077>\
**Category:** Video SDK\
**Tags:** video-sdk, android\
**Created:** [January 22, 2025, 11:27am UTC](https://devforum.zoom.us/t/metadata-buffer-for-crash-for-android/125077 "2025-01-22T11:27:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![paul.mathew](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/paul.mathew/32/53727_2.png) [@paul.mathew](https://devforum.zoom.us/u/paul.mathew)\
**Post date:** [January 22, 2025, 11:27am UTC](https://devforum.zoom.us/t/metadata-buffer-for-crash-for-android/125077/1 "2025-01-22T11:27:55Z")

</div>

This is the sdk that we are using implementation(“us.zoom.videosdk:zoomvideosdk-core:2.1.0”)

and while 2 people are in a call after 9 min the call is getting disconnected automatically and getting the error like below

16:40:47.148 Camera2-Metadata app\_id resizeIfNeeded: Can’t allocate larger metadata buffer  
16:40:47.149 app\_id updateImpl: Unable to update metadata entry android.lens.info.shadingMapSize (90006): Out of memory (-12)  
16:40:47.198 libc++abi app\_id terminating due to uncaught exception of type St9bad\_alloc: std::bad\_alloc  
16:40:47.497 app\_id terminating with uncaught exception of type std::bad\_alloc: std::bad\_alloc  
16:40:47.501 app\_id terminating with uncaught exception of type std::bad\_alloc: std::bad\_alloc  
16:40:47.501 app\_id terminating due to uncaught exception of type St9bad\_alloc: std::bad\_alloc  
16:40:47.502 app\_id terminating due to uncaught exception of type std::bad\_alloc: std::bad\_alloc  
16:40:47.502 app\_id terminating with uncaught exception of type std::bad\_alloc: std::bad\_alloc  
16:40:47.502 app\_id terminating with uncaught exception of type std::bad\_alloc: std::bad\_alloc  
16:40:48.208 ConnectivityService system\_server RemoteException caught trying to send a callback msg for NetworkRequest [LISTEN id=16098, [ Capabilities: INTERNET&NOT\_RESTRICTED&TRUSTED&FOREGROUND&NOT\_VCN\_MANAGED&NOT\_BANDWIDTH\_CONSTRAINED Forbidden: LOCAL\_NETWORK Uid: 10570 RequestorUid: 10570 RequestorPkg: app\_id UnderlyingNetworks: Null] ]  
16:40:48.208 system\_server RemoteException caught trying to send a callback msg for NetworkRequest [TRACK\_DEFAULT id=16101, [ Capabilities: INTERNET&NOT\_RESTRICTED&TRUSTED&NOT\_VCN\_MANAGED&NOT\_BANDWIDTH\_CONSTRAINED Uid: 10570 RequestorUid: 10570 RequestorPkg: app\_id UnderlyingNetworks: Null] ]  
16:40:48.209 system\_server RemoteException caught trying to send a callback msg for NetworkRequest [LISTEN id=16108, [ Capabilities: INTERNET&NOT\_RESTRICTED&TRUSTED&NOT\_VPN&FOREGROUND&NOT\_VCN\_MANAGED&NOT\_BANDWIDTH\_CONSTRAINED Forbidden: LOCAL\_NETWORK Uid: 10570 RequestorUid: 10570 RequestorPkg: app\_id UnderlyingNetworks: Null] ]  
16:40:48.969 InputDispatcher system\_server channel ‘e99d96d app\_id/com.taskhuman.videocallfeature.zoom.ZoomActivity’ ~ Channel is unrecoverably broken and will be disposed!

can someone help me with this  
@chunsiong.zoom@rehema.zoom@tommy@jon.zoom

---

<div class="post-metadata">

**Author:** ![paul.mathew](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/paul.mathew/32/53727_2.png) [@paul.mathew](https://devforum.zoom.us/u/paul.mathew)\
**Post date:** [January 23, 2025, 1:36pm UTC](https://devforum.zoom.us/t/metadata-buffer-for-crash-for-android/125077/2 "2025-01-23T13:36:17Z")

</div>

@ekaansh.zoom Can you help me here …  
while the users are in the call memory leak is happening .  
**2.7GB For Native memory**  
Right now I’m using this version  
implementation(“us.zoom.videosdk:zoomvideosdk-core:2.1.0”)

 ![Screenshot 2025-01-23 at 19.05.13](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/9/d/9dadcd135a6d75051611fba02a13f5d3eefd5857.png)

---

<div class="post-metadata">

**Author:** ![ekaansh.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ekaansh.zoom/32/55004_2.png) [@ekaansh.zoom](https://devforum.zoom.us/u/ekaansh.zoom)\
**Post date:** [January 23, 2025, 2:01pm UTC](https://devforum.zoom.us/t/metadata-buffer-for-crash-for-android/125077/3 "2025-01-23T14:01:25Z")

</div>

Hey @paul.mathew thanks for flagging, let me check with engineering.

---

<div class="post-metadata">

**Author:** ![paul.mathew](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/paul.mathew/32/53727_2.png) [@paul.mathew](https://devforum.zoom.us/u/paul.mathew)\
**Post date:** [January 23, 2025, 2:03pm UTC](https://devforum.zoom.us/t/metadata-buffer-for-crash-for-android/125077/4 "2025-01-23T14:03:38Z")

</div>

thank you … @ekaansh.zoom  
what is happening right now is that.  
calls are getting dropped automatically after 10 min or so.

---

<div class="post-metadata">

**Author:** ![paul.mathew](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/paul.mathew/32/53727_2.png) [@paul.mathew](https://devforum.zoom.us/u/paul.mathew)\
**Post date:** [January 28, 2025, 6:27am UTC](https://devforum.zoom.us/t/metadata-buffer-for-crash-for-android/125077/5 "2025-01-28T06:27:31Z")

</div>

@ekaansh.zoom hi,  
any update for this?

---

<div class="post-metadata">

**Author:** ![ekaansh.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ekaansh.zoom/32/55004_2.png) [@ekaansh.zoom](https://devforum.zoom.us/u/ekaansh.zoom)\
**Post date:** [February 3, 2025, 1:10pm UTC](https://devforum.zoom.us/t/metadata-buffer-for-crash-for-android/125077/6 "2025-02-03T13:10:48Z")

</div>

Sorry, still working on this one. I’ll share here once I have an update.
