Hi there! On Thu, 19 Jun 2003, David McKee wrote:
Folks, I've been using dillo for a number of months now, and it has become my first choice browser--I switch to mozilla or opera only when I have to java, javascript, http/1.1 authentication, ssl and the like.
I like that part! :) Well, this thread has had a lot of post, and bugfixes! The problem is that we don't yet find a way to reproduce the original problem, that is:
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 [...]
N.B. I seems to happen most when I have opened several links in new windows in rapid succession.
(I also hinted howto try to reproduce it in this thread). Now a "blind fix" is in the CVS. That is, new code that fixes all the lose ends in IO.c and file.c, I was able to find, about EINTR. If some of the file descriptor, for instance, happened to be interrupted inside the 'close' call (returning EINTR), and remained open, could be the cause of the CPU HOG (by not being eliminated from the FDset inside GTK+ code). What does it mean? If someone finds a way to reproduce the HOG (with older code) and it doesn't happen with the CVS, then it's fixed! If someone reproduces the bug with the newest CVS code, then the bug is hiding elsewhere... Cheers Jorge.-