cristiangreco (Cristian Greco)
- Login: cristiangreco
- Registered on: 10/23/2019
- Last sign in: 11/18/2020
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
10/27/2019
-
08:41 PM Ruby Bug #16278: Potential memory leak when an hash is used as a key for another hash
- Thanks both @jeremyevans0 @alanwu for the rich and clear explanations!
10/26/2019
-
- Hi Jeremy, thanks for these details!
I don’t know the details of ruby’s GC, seems to me it might behave unpredictably sometimes. I guess what confuses me now is that although that object is retained we don’t observe unbounded memory g...
10/25/2019
-
- jeremyevans0 (Jeremy Evans) wrote:
> `object_id` is only unique for the life of the object. After the object is garbage collected, the same `object_id` could be used for a different object. So measuring using `object_id` is not a go... -
- ko1 (Koichi Sasada) wrote:
> > If an application exercises this pattern very frequently during lifetime and across multiple processes then it’s definitely going to bloat memory, at the very least. As a real-world example, this is causin...
10/24/2019
-
- mame (Yusuke Endoh) wrote:
> This code uses constant memory. If it caused memory leak, the memory usage would continue to increase.
Thank for your answer!
If an application exercises this pattern very frequently during lifetime...
10/23/2019
-
- Hi,
I've been hitting what seems to be a memory leak.
When an hash is used as key for another hash, the former object will be retained even after multiple GC runs.
The following code snippet demonstrates how the hash `{:a => 1}`...