
10 Apr
2008
10 Apr
'08
11:18 p.m.
I've looked into this further and I believe the leaked connections are due to Network.Browser, this is a separate issue from that identified by Paul Brown. The BrowserState in Network.Browser has a connection pool of up to five connections. When a sixth is opened the oldest connection is closed. This looks to be the only time that a connection is closed. BrowserState's internals are not exported so there is no way for a user to close them. The net effect for HXT is that every time readDocument is called, using native http, a single TCP connection is leaked. I've attached a patch against the darcs version of http that cures my test programs leak. Cheers Daniel