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
After reading the doc of cc, I still now get how CC can help tracking the Reference Counting problem. In Netty, there is a pooled ByteBuf, which will report as Memory LEAK if the bytebuf get gced but with referenceCnt > 0.
Can CC helps here?
defuseByteBuf() :Unit{withByteBuf{buf =>valbytes=ByteBufUtil.getBytes(buf) // some usage never call byteBuf.release } } defwithByteBuf( op: ByteBuf^=>Unit):Unit={valallocator= pooledByteBufAllocator valbuf= allocator.byteBuf(1024) op(buf) //... never call byteBuf.release }
Can CC help and reporting the byteBuf.release is not called?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
After reading the doc of cc, I still now get how CC can help tracking the Reference Counting problem.
In Netty, there is a pooled
ByteBuf, which will report as Memory LEAK if the bytebuf get gced but with referenceCnt > 0.Can CC helps here?
Can CC help and reporting the
byteBuf.releaseis not called?BetaWas this translation helpful?Give feedback.
All reactions