Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Can CC helps tracking the Reference Counting problem?#18556

He-Pin started this conversation inCC experiment
Discussion options

After reading the doc of cc, I still now get how CC can help tracking theReference Counting problem.
In Netty, there is a pooledByteBuf, 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= pooledByteBufAllocatorvalbuf= allocator.byteBuf(1024)   op(buf)//... never call byteBuf.release}

Can CC help and reporting thebyteBuf.release is not called?

You must be logged in to vote

Replies: 0 comments

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
1 participant
@He-Pin

[8]ページ先頭

©2009-2025 Movatter.jp