[Dillo-dev]Re: Dillo Bug #650 partial workaround
On Thu, Dec 23, 2004 at 04:56:22PM -0500, Roberto Sanchez wrote:
Jorge Arellano Cid wrote:
On Sun, Dec 19, 2004 at 01:04:08AM -0500, Roberto Sanchez wrote:
Jorge,
I have a partial workaround for bug #650. It is not exactly pretty. The problem is that the website reported in the bug, www.ilsole24ore.it, does not send a Content-Type header. The result is:
Nav_open_url: Url=>http://www.ilsole24ore.it<; Dns_server [0]: www.ilsole24ore.it is 0x80b97f8 Connecting to 212.45.97.54 HTTP warning: Server didn't send Content-Type in header.
[...]
My investigation on this is leading to a patch that will enable Dillo to wait for more input when there's not enough data at HTTP header-parsing time (to detect the content-type).
This is the same problem you face when a SGML comment that's to be skipped is trimmed in the middle by the TCP packetizing.
The good news is that when I'm done, the patch you're working on will be much easier to complete.
OK. I have started on this, but have only put a few hours into it. I will wait for your patch.
Done. It took a couple of days to commit because of christmas ;-).
You can work on:
<q> there is a small memory leak in the current CVS version of Dillo: The trivial document
<html><head><title>memory leak</title></head><body></body></html>
produces on exiting Dillo:
** WARNING **: 1 styles left ** WARNING **: 1 fonts (1 references) left ** WARNING **: 1 colors (1 references) left
What do these warnings mean?
That some reference-counted styles of Dw are not being freed.
Where can I find out more about them?
./srch a_Dw_style_ref or ./srch a_Dw_style_unref
Does this indicate that objects were allocated and never released?
Yes. ======== List readers: Roberto just joined us as a contributing developer. We've had some email interchange out of dillo-dev band to set things up. Now we'll continue writing on the list. Welcome aboard! -- Cheers Jorge.-
participants (1)
-
Jorge Arellano Cid