Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Handler Never Gets Deleted #3

Closed
bfrog opened this Issue Aug 11, 2010 · 2 comments

Comments

Projects
None yet
3 participants

bfrog commented Aug 11, 2010

del for my websockethandler never gets called, the object is never freed even when connections are lost

Wuushu commented Aug 12, 2010

if in your program in the def connectionLost():

if you add a del self; does it help?

Bfrog, does your init method get called twice for each connection? (I added a debug-print statement and it prints twice: http://github.com/rlotun/txWebSocket/issues#issue/2)

Owner

rlotun commented Dec 23, 2010

Fix some memory leaks.

We now explicity del references to objects as connections are dropped.
Also, there was a small bug in the example where the loopingCall had
to be deled for the Handler object to be garbage collected.

Closed by ee31d15

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment