I give up (How the heck can *that* be leaking?)

Somehow a test case which consists of creating a client, calling getTable( ) on it, and having it immediately raise a socket error when it goes to send is leaking. There must be something going wonky at the Twisted level. Maybe a deferred/callLater object getting left on the stack for every call? Maybe a demon? Maybe an imp or a gremlin?

Anyway I give up for today. I've been going since 9 in the morning and it's just not getting me anywhere. The solution must be trivially simple, but I'm just spinning my wheels on it. So, scr#w it, I'm going to do something else for a few days and then go back to worrying this bone.


Comments are closed.


Pingbacks are closed.