From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Fri Mar 20 12:15:34 EDT 2020
Received: from abbatoir.fios-router.home (pool-162-83-132-245.nycmny.fios.verizon.net [162.83.132.245])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 2219d30c (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Fri, 20 Mar 2020 09:15:26 -0700 (PDT)
Message-ID: <2E9D0BC175C6CB97ED70074A091C37A7@eigenstate.org>
To: knusbaum@sdf.org, 9front@9front.org, kokamoto@hera.eonet.ne.jp
Subject: Re: [9front] adding javascript enable to netsurf
Date: Fri, 20 Mar 2020 09:15:24 -0700
From: ori@eigenstate.org
In-Reply-To: <DA2CE2F0-7628-4126-8908-AFA5E93E2193@sdf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: virtual session-oriented injection property backend 

> I think the error is due to a limitation of the webfs fetcher. Currently, the fetcher hangs on
> to webfs handles until they're freed by netsurf, even after the data is
> read, because after they're closed things like headers are unavailable.
> This means tha webfs handles can be exhausted, at which point netsurf
> starts to run into that error.
> 
> This can definitely be improved in the webfs fetcher, but maybe the
> relatively low webfs handle limit could also be raised.
> 

Are they ever released, or are they effectively leaked?

Also, searching on Google just.. doesn't work. It seems like we get
a bogus URL.