From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx.sdf.org ([205.166.94.20]) by ewsd; Fri Mar 20 18:08:01 EDT 2020 Received: from [192.168.0.16] (c-98-212-152-230.hsd1.il.comcast.net [98.212.152.230]) (authenticated (0 bits)) by mx.sdf.org (8.15.2/8.14.5) with ESMTPSA id 02KM7qbf000234 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128 bits) verified NO); Fri, 20 Mar 2020 22:07:53 GMT Date: Fri, 20 Mar 2020 17:07:48 -0500 User-Agent: K-9 Mail for Android In-Reply-To: <2E9D0BC175C6CB97ED70074A091C37A7@eigenstate.org> References: <2E9D0BC175C6CB97ED70074A091C37A7@eigenstate.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9front] adding javascript enable to netsurf To: ori@eigenstate.org, 9front@9front.org, kokamoto@hera.eonet.ne.jp From: Kyle Nusbaum Message-ID: <6676E151-594B-4DC5-BA96-07D7CFB0EEFE@sdf.org> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: RESTful proven HTML over SQL content-driven dependency controller They are released when netsurf releases the resource handles, usually when = it's done loading the page, but I'm not sure exactly what triggers it=2E Id= eally the webfs handles would be released when the content was done being f= etched=2E I guess Google (and every other webform) is broken because of the iconv th= ing=2E I noticed this when I first started working on it=2E The problem doe= sn't come from within the webfs fetcher and I didn't take the time to track= it down=2E Fixing that would really help make the existing netsurf useful= =2E=20 On March 20, 2020 11:15:24 AM CDT, ori@eigenstate=2Eorg wrote: >> I think the error is due to a limitation of the webfs fetcher=2E >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=2E >> This means tha webfs handles can be exhausted, at which point netsurf >> starts to run into that error=2E >>=20 >> This can definitely be improved in the webfs fetcher, but maybe the >> relatively low webfs handle limit could also be raised=2E >>=20 > >Are they ever released, or are they effectively leaked? > >Also, searching on Google just=2E=2E doesn't work=2E It seems like we get >a bogus URL=2E -- Kyle