View Revisions: Issue #536
[ Back to Issue ]
| Summary | 0000536: Netsurf 2.7 on Google 'Failed writing body' error | ||
|---|---|---|---|
| Revision | 2011-07-26 13:45 by Bernard Veasey | ||
| Description | Over the last few weeks I have been getting the following error when visiting www.google.co.uk sometimes: Warning from NetSurf Failed writing body (0 != 249) Continue When I click continue the page remains blank. When I click the Netsurf icon on the icon bar a second time, it usually works but sometimes it repeatedly fails to load with the same error every time. I have only had this error with the Google page. All other sites I have tried work OK as usual. My telephone exchange has recently been upgraded to 21CN and my broadband connection has been upgraded to ADSL2+ a few weeks ago as well. I don't know if there is a connection but the error and upgrade both started around the same time. I am using an Iyonix PC with RISC OS 5.16 (512MB memory) with the latest stable NetSurf 2.7 I also have a Windows PC and www.google.co.uk has never produced an error on that. |
||
| Revision | 2013-12-12 12:28 by Vincent Sanders | ||
| Description | Over the last few weeks I have been getting the following error when visiting www.google.co.uk sometimes: Warning from NetSurf Failed writing body (0 != 249) Continue When I click continue the page remains blank. When I click the Netsurf icon on the icon bar a second time, it usually works but sometimes it repeatedly fails to load with the same error every time. I have only had this error with the Google page. All other sites I have tried work OK as usual. My telephone exchange has recently been upgraded to 21CN and my broadband connection has been upgraded to ADSL2+ a few weeks ago as well. I don't know if there is a connection but the error and upgrade both started around the same time. I am using an Iyonix PC with RISC OS 5.16 (512MB memory) with the latest stable NetSurf 2.7 I also have a Windows PC and www.google.co.uk has never produced an error on that. |
||
| Revision | 2011-07-26 13:45 by Bernard Veasey | ||
| Additional Information | kyllikki1 added a note on Thu Jun 6 16:18:11 2013 Thank you for taking the time to report this bug and helping to make NetSurf better. However, I am closing it because the bug seems to have been fixed in the latest development version of NetSurf. Please, try to reproduce this bug using the latest version. If the bug still exists, feel free to file a new report with an updated version number. nobody added a note on Sun Nov 20 18:09:09 2011 I also had this problem with the Atari port at the beginning. It was caused by an network bug within the kernel / socket API. The socket was reported to be writable right after connect(), which isn't correct - first it has to establish the TCP connection. If you write to the socket altough the connect() isn't finished. you will get exactly this error. bapfish added a note on Thu Aug 25 08:14:32 2011 I have tried upgrading to the latest beta release - r12644 23 Aug 2011 - and the problem remains. It also happens occasionally on other websites, not just Google. It goes wrong about 30 times a day for me at the moment and is a real pain. Imported from sourceforge bug #3378546 on Tue Dec 10 17:34:12 2013 |
||
| Revision | 2013-12-12 12:28 by Vincent Sanders | ||
| Additional Information | kyllikki1 added a note on Thu Jun 6 16:18:11 2013 Thank you for taking the time to report this bug and helping to make NetSurf better. However, I am closing it because the bug seems to have been fixed in the latest development version of NetSurf. Please, try to reproduce this bug using the latest version. If the bug still exists, feel free to file a new report with an updated version number. nobody added a note on Sun Nov 20 18:09:09 2011 I also had this problem with the Atari port at the beginning. It was caused by an network bug within the kernel / socket API. The socket was reported to be writable right after connect(), which isn't correct - first it has to establish the TCP connection. If you write to the socket altough the connect() isn't finished. you will get exactly this error. bapfish added a note on Thu Aug 25 08:14:32 2011 I have tried upgrading to the latest beta release - r12644 23 Aug 2011 - and the problem remains. It also happens occasionally on other websites, not just Google. It goes wrong about 30 times a day for me at the moment and is a real pain. Imported from sourceforge bug #3378546 on Tue Dec 10 17:34:12 2013 |
||