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
Capacity: 0
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Leak',
When I trace the alloc/free calls, there is indeed a leak: the HashMap backing one of the shards is leaked. Since the capacity is zero at this time, there should not be any hashmaps still active.
When using the random hasher, the problem is difficult to reproduce which is why I switched to the default hasher, and then found a particular offset (9) which exhibits the problem.
Interestingly, I've only observed the problem with string keys. With integer keys I could not reproduce the issue.
The problem occurs exactly the same in both debug and release builds.
The text was updated successfully, but these errors were encountered:
This is... confusing to say the least.
The following program (a minimized form of the problem I am experiencing in the wild) demonstrates what I believe to be a memory leak in DashSet.
When run, the program prints the following:
When I trace the alloc/free calls, there is indeed a leak: the
HashMap
backing one of the shards is leaked. Since the capacity is zero at this time, there should not be any hashmaps still active.When using the random hasher, the problem is difficult to reproduce which is why I switched to the default hasher, and then found a particular offset (9) which exhibits the problem.
Interestingly, I've only observed the problem with string keys. With integer keys I could not reproduce the issue.
The problem occurs exactly the same in both debug and release builds.
The text was updated successfully, but these errors were encountered: