On Sat, Feb 23, 2008 at 1:57 PM, Matthew Toseland <toad at amphibian.dyndns.org> wrote:
> On Saturday 23 February 2008 00:07, Ian Clarke wrote: > > Just upgraded to the current testing snapshot (sh update.sh testing), > and I > > am still finding that it takes a rediculous amount of time for FProxy to > > show up the first time (my browser has now been hanging for well over a > > minute). > > Define "hanging". The browser is requesting the fproxy page, but *none* of the page has been delayed yet. > According to the below thread dump, fproxy is fetching > something from Freenet. Presumably this is one of the activelinks, so when > you say your browser is hanging, you mean it hasn't finished loading all > the > images on the front page? No, none of the front page has loaded. > Given that the front page contains activelinks (which are sourced from > freesites), it's not so unreasonable to expect it to take a while to > completely finish loading the pictures (especially as this involves > loading > the whole container which can be quite big in many cases). Having said > that, > when I have tested this it has occasionally appeared to me that fproxy > requests started before freenet has any connections can get stuck and not > complete even when it does get some. I will investigate. As I mention above, its not just a few images on the page that aren't loading, its the entire page. Clearly this is a fatal usability problem, any newbie that had just installed Freenet would be stopped in their tracks at this point - and we would have lost a potential user. Ian. -- Email: ian at uprizer.com Cell: +1 512 422 3588 Skype: sanity -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20080224/7879a1b6/attachment.html>
