Matthias, On Wed, Oct 06, 2004 at 01:52:40PM +0200, Matthias Franz wrote:
Hi everybody,
the rendering is really much better in the 0.8.3 version. Well done!
Unfortunately, I'm experiencing problems with the new version that I've never had with 0.8.2:
1. Dillo displays a page without the embedded GIF image, showing the alternate text instead. It starts consuming all cpu time, but still responds to keyboard and mouse input (history navigation; no new pages are displayed).
2. Dillo doesn't display a page at all. Cpu/input behaviour as before.
The problems only occur with certain local files, not http pages. Moreover, they don't occur deterministically. They seem to happen somewhat more often if one follows a link instead of loading a page from the command line.
The "bad" pages are from some documentation I've written, available at http://www-fourier.ujf-grenoble.fr/~franz/convex/doc/current/ . But remember that so far the problems have only occurred with local files. You can download the complete documentation (roughly 80 kB) at http://www-fourier.ujf-grenoble.fr/~franz/convex/files/current/convex-doc.ta... (gunzip it in a new directory).
Problem 1 occurs with the page "about.html" (link "About this document" on the main page "index.html"). It happens in about 50% of all cases. It does not depend on the setting of w3c_plus_heuristics in dillorc.
Problem 2 ocurred so far with the pages "PFACE.html" (link: Operators and functions "for PFACE") and "GFDL.html" (link "GNU free document license"). This problem is extremely rare, though (2 or 3 times in all).
I tried a few times with and without dpid already running and can't reproduce it on my machine. I'll keep trying to get a way or hint on it, this is just to let you know. It is very hard to try to debug a problem you don't know how to reproduce. The good news is that I found a way to crash the current file-dpi by hitting reload quickly. This didn't happen with 0.8.2, so I'll start investigating here hoping it gets me to the root of the same problem. If someone here on the mailing list can reporduce it at home, a report on how it happens or not would also be welcomed.
[...] Sorry for reporting the bug rather late after Jorge's email, but I came across this problem only yesterday.
No problem. It looks like we'll have to delay the release and make an rc2. -- Cheers Jorge.- PS: I kept waiting some patches from you. What happened? Or is it my head that lost track of them... ;-)