On Fri, 20 Jun 2003, Frédéric Bothamy wrote:
* David McKee <dmckee@jlab.org> [2003-06-19 13:46] :
[...] Of late dillo has started getting into a state where all progress stop in all open windows, and it sits on the CPU---keeping my load average at 1.0
[...] So, two questions:
-- Has anyone else observed this behavior?
Not sure if the problem is the same, but I have noticed this behaviour when I load a big page with an anchor (or is it a reference?) in the address, eg:
http://ftp-master.debian.org/testing/update_excuses.html#kdelibs
(WARNING: 853 Kb). It eventually finishes loading the page but it can take a HUGE amount of time (several minutes whereas the same page without '#kdelibs' only takes about 10 to 15 seconds).
This is another problem! IIRC Sebastian posted a comment about this sometime ago, but although I searched for, I didn't find the post :( After reviewing it myself (the huge page with anchor problem), I developed a small patch that more or less solves the problem (makes the anchored URL to load two times slower, but it works). -- I'm still working on it. The problem is similar to what we had before incremental rewraping. The anchor (aka. "fragment") code falls inside an exponential algorithm so it dies hogging (unless you have exponential patience!).
I do not think however that this particular problem is specific to Dillo as I have already seen Mozilla hung with the same test.
Most programs don't care much about hogging the CPU, but we do! So this is a BUG in Dillo and we'll try to work it out. Sebastian: Did you post something about this, or is it my mind joking on me? Cheers Jorge.- PS: The search for a way to reproduce the other BUG is still open