Bobi Tena III

during our test, I can see ByteBufferPool upto 3000+... is this a memory leak? meaning jvb won't be able to recover the heap memory during garbage collection? @bbaldino

so it is possible that jvb heap memory (default 3GB) will be consumed by this buffer allocation when it received a continuous large buffer that is more than 1500 bytes?...

> > so it is possible that jvb heap memory (default 3GB) will be consumed by this buffer allocation when it received a continuous large buffer that is more than...

> @gtena378 You should obtain a heap dump with jmap. Then, browsing it with visualvm, one can see where is memory being consumed. > > Without data, it is imposible...

now we collected heap dump but can't identify if there's a memory leak  during our testing I've seen a lots of warning log of bytebufferpool  at that moment...

We encountered out of memory here's the details: https://community.jitsi.org/t/how-to-force-jvb2-take-momory-more-than-4gb/28143/7 here's the heap dump:  there's a lot of byte[] and ArrayCache$Container instance

We tried to change the T3 size in ByteBufferPool from 1500 to 2700 and compiled it. During our crowd testing with 28 participants we didn't encountered ByteBufferPool warning but still...