On 27th January 2013 David Pitt wrote most cogently:
> I have saved logs from a successful fetch with NetSurf 2.9 and a
> timeout from NetSurf 3.0 #833. The full logs are at :-
>
> http://pittdj.co.uk/temp/NSlogs.zip
>
> The interesting bits are :-
>
> NetSurf 3 #833 on Mac OS 10.8.2 - timed out
>
> (3.240000) desktop/browser.c browser_window_go_post 855: bw
> 0x25baa658, url http://www.google.co.uk/
> (3.240000) desktop/browser.c browser_window_go_post 976: Loading
> 'http://www.google.co.uk/'
> (3.240000) content/fetchers/curl.c fetch_curl_setup 366: fetch
> 0x25bd8120, url 'http://www.google.co.uk/'
> (33.250000) content/fetchers/curl.c fetch_curl_done 843: done
> http://www.google.co.uk/
> (33.250000) content/fetchers/curl.c fetch_curl_done 880: Unknown cURL
> response code 28
> (33.250000) content/fetchers/curl.c fetch_curl_stop 725: fetch
> 0x25bd8120,
> url 'http://www.google.co.uk/'
> (33.260000) riscos/gui.c warn_user 2339: Resolving timed out after
> 30000 milliseconds (null)
>
> NetSurf 2.90 on Mac OS 10.8.2 - successful
>
> (2.990000) desktop/browser.c browser_window_go_post 832: bw
> 0x25ba6948, url http://www.google.co.uk/
> (2.990000) desktop/browser.c browser_window_go_post 953: Loading
> 'http://www.google.co.uk/'
> (2.990000) content/fetchers/curl.c fetch_curl_setup 365: fetch
> 0x25b99e08,
> url 'http://www.google.co.uk/'
> (3.200000) content/fetchers/curl.c fetch_curl_process_headers 1171:
> HTTP status code 200
> (3.200000) content/fetchers/curl.c fetch_curl_done 813: done
> http://www.google.co.uk/
> (3.200000) content/fetchers/curl.c fetch_curl_stop 695: fetch
> 0x25b99e08,
> url 'http://www.google.co.uk/'
I am still having the same problem with bleeding edge development
versions, though 2.9 works well.
Does anyone have a resolution of this problem, or are there any
prospects of a resolution?
--
Tim Powys-Lybbe tim@powys.org
for a miscellany of bygones: http://powys.org/
No comments:
Post a Comment