-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Methods that continuously call WeakReference wrapper may throw an NPE #446
Comments
Yes, this does happen when the system gc occur, maybe we can use strong reference instead of weak reference. |
I need to continue to understand the business logic in order to understand the author's intentions. We can wait for more comments on this question. |
The weak reference of You are right. When system GC occurs, weak references will be recycled, but if the strong reference of ClientGroupWrapper also exists, maybe it will not be a problem. We can find strong reference in the
|
It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature. If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue. |
@Pil0tXia, pls assigned this issue to me. |
@zzzk1 OK |
Community member explained why the design is like this and why there is no need to worry about the potential weak reference problem (#446 (comment)). Could anyone explain why this viewpoint is not recognized and this issue must be fixed? 社区成员解释了为什么这样设计以及为什么不需要担心弱引用的潜在问题(#446 (comment) ),谁能解释一下该观点不被认可、必须修复该issue的原因? |
Closed after #4872 (comment). |
All methods using
WeakReference
must check whether it isNULL
after callingget()
.The text was updated successfully, but these errors were encountered: