Rolf Leggewie
Mon, 23 Apr 2001 21:48:03 -0700
Hi Andrew, thank you for your comments. "Andrew M. Bishop" wrote: >> correctly. The version is 2.6a on a 233 Mhz Pentium II running English >> Windows 95a. My browsers (NS4.76 and IE5) point to the proxy >> 127.0.0.1:8080. > > I don't think that there have been any reports of it working on > Win95a. It has been tested on Win98, WinME & Win2000 and is known to > work on them. http://www.rebirthing.co.nz/wwwoffle/ claims it runs on Win95, too. >> stops and nothing happens. WWWOffle displays the message >> "wwwoffled[110865] Important: Child wwwoffles terminated by signal 11 >> (pid=1908093)." That is all. The program displays the same behaviour >> for all URLs. > > The "signal 11" means that the program is crashing due to a > segmentation fault. Do I understand the term correctly as a problem relating to memory management (two programs trying to access the same memory space) ? Indeed, when I start Windows while holding the shift key[1] and use ctrl-alt-del to kill all processes not really necessary[2], WWWOffle runs on my system but still quite unstable. I have fetched a few pages from another local proxy and sometimes "signal 11" doesn't occur for a dozen or so pages. So my guess is that WWWOffle has problems in interacting and sharing the memory with other programs at least under Windows. From my observations, it appears that other Internet related programs (local newsserver Hamster, local proxy Nearsite) are the most troublesome. But as I said, even on its own with just a barebones Windows running, the program has problems, just a lot less frequently. Can somebody please comment on the possibility that this is indeed a memory related bug ? Thank you. Regards Rolf Footnotes: ========== [1] Startup Folder is bypassed. [2] Memory space is freed to the max, minimizing the risk of two programs trying to access the same memory space