gregoriusxu / booksleeve

Automatically exported from code.google.com/p/booksleeve
Other
0 stars 0 forks source link

Leaked RedisConnection objects after dispose. #49

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create a RedisConnection to a valid server.
2. Open the connection.
3. Dispose of the connection.
4. Take a memory snapshot with your memory profiler of choice.

What is the expected output? What do you see instead?
I would expect to see the RedisConnection object in the finalization queue. 
Instead there is a lingering SocketAsyncEventArgs preventing the connection 
from being garbage collected.

What version of the product are you using? On what operating system?
v1.3.39

Please provide any additional information below.
The readArgs instance var of RedisConnectionBase is never disposed of. That 
object holds onto a RedisConnection reference via the 
SocketAsyncEventArgs.Completed event delegate.

Fixed via: 
https://code.google.com/r/agcastle64-booksleeve/source/detail?r=5168fee3e1fcedc5
070fdb252b3052b6eeaef247

Original issue reported on code.google.com by agcastl...@gmail.com on 30 Oct 2013 at 2:47