From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx.sdf.org ([205.166.94.20]) by ewsd; Fri Mar 20 12:13:06 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 02KGAq23016014 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128 bits) verified NO); Fri, 20 Mar 2020 16:10:54 GMT Date: Fri, 20 Mar 2020 11:10:48 -0500 User-Agent: K-9 Mail for Android In-Reply-To: <505E2F5D4E24CB55E635874D76DD7759@hera.eonet.ne.jp> References: <505E2F5D4E24CB55E635874D76DD7759@hera.eonet.ne.jp> 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: 9front@9front.org, kokamoto@hera.eonet.ne.jp From: Kyle Nusbaum Message-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: abstract blockchain rich-client standard session solution 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 This can definitely be improved in the webfs fetcher, but maybe the relatively low webfs handle limit could also be raised=2E On March 20, 2020 12:49:35 AM CDT, kokamoto@hera=2Eeonet=2Ene=2Ejp wrote: >I worked more on nsfb on arm=2E >Yes, js codes are read successfully now, I have another >unexpected text messages on the screen=2E=2E=2E > >But the way: >What means "Failed to clone webfs: Error '/mnt/web/clone' no more >client" >I see this errors for 19 times, and then suicide > >Kenji -- Kyle