Re: [Themis-dev] HTML parser hang...

[Raymond C. R. <ra...@ba...>]

Mark Hellegers wrote:
>> I was running some tests to see if I could find a sign of the error that
>> Mark was referring to about the HTML parser getting the wrong content,
>>     
> and
>   
>> ran into some odd behavior on a fairly simple page I wrote specifically
>>     
> for
>   
>> simple testing: http://www.dmsfriend.com/themistest.html . Basically, the
>> parser would get the content and begin going through it, but would stop
>> suddenly without error or message until the window was closed, at which
>> point it would continue.
>>
>> I'm attaching two files to this message. The first is hang_point.txt
>>     
> which
>   
>> contains the output immediately preceding the hang, including the spot
>>     
> where
>   
>> it hung in the middle of outputting some text. The second is
>>     
> all_output.txt
>   
>> which contains all of the output from that execution, including the hang,
>> and the output generated when the window was closed.
>>
>> The easiest way to sync up the two files is to do a search for "Time
>>     
> taken
>   
>> for loading the schema: 1.270000" in each and then scroll to the end of
>>     
> the
>   
>> output in hang_point.txt.
>>
>> The Themis build was on Haiku r29147 built on 2/7/2009 (a build I did
>> myself), with only the cache, http, and html parser add-ons. Admittedly,
>>     
> the
>   
>> code used still does have some uncommitted changes in the http add-on but
>>     
> I
>   
>> don't think they're related to this hanging issue.
>>     
>
> Hi Raymond,
>
> I tested the website on an R5 system and it parses it without problems
> here.
> It seems to stop in the middle of a printf call on your system, which is
> strange.
> If it keeps happening consistently there is probably a bug in Haiku.
>
>
>   
You're probably right, though I suppose could also be something in the 
cache code; perhaps it's not providing all of the data to the parser for 
some reason. I really wish I had a system capable of running R5 to 
compare and test with. :-/ I'll zip up the directory later and post it 
online; please [try to] compile it and see if you run into any problems 
with it when you get a chance. That will eliminate or verify that my 
code changes are the cause.

Thanks Mark!
Raymond