In message <6b7a725f50.zen44...@zen.co.uk>
Simon Smith <simon_sm...@zen.co.uk> wrote:
> In message <505f6e90cet...@netsurf-browser.org>
> Michael Drake <t...@netsurf-browser.org> wrote:
>
> > In article <b19b2a5f50.zen44...@zen.co.uk>,
> > Simon Smith <simon_sm...@zen.co.uk> wrote:
> >
> >
> > > I'm still managing to trigger socket exhaustion from time to time - in
> > > fact I think I'm getting better at it.
> >
> > 1. What version of NetSurf are you using? This was a known problem with
> > development builds for a period a couple of years back.
> >
> > 2. NetSurf allows the number of simultaneous connections it makes to be
> > controlled. What values do you have in the Fetching section of
> > Choices... Connection?
> >
> > 3. Try reducing the values.
> >
> > Michael
>
> I'm currently on build 7512 of 14/05/2009
>
> I usually update every 1-3 weeks.
>
> Max fetches 24
> Fetches per host 20
> Cached connections 6
I'm now on the fresh 2.1 release, and the problem is as bad as ever. In
particular, using a recent URL from the pull-down list, then selecting
another recent URL /in the same window/ before the first page has loaded
also seems to trigger it. So it's very easy by various means to accidentally
get NetSurf in a state where the next aborted download will drop the socket
count to zero. A nuisance.
--
Simon Smith
Where there's muck there's hope.
