On Thu, 26 May 2011 03:34:06 -0400, reza farivar <rf.opensource@gmail.com> wrote:
Hi guys,
First post here, thanks for all your hard work on Dillo! I'm trying to compile and run dillo on Mac OS 10.6.7 (and report the bugs I find :D ). I followed instructions that Jorge sent me earlier, and it compiled without an error but a few warnings:
[...]
The good news is that Dillo runs. It also seems to eventually connect to websites, which is good news too.
But at least for me loading a page is a hit or miss experiment. Sometimes it waits for a long time (maybe 2-3 minutes) and couldn't connect, as if there was a DNS problem, other times it loads the same page easily in a few seconds. Here's the output from the terminal, after trying to connect to yahoo.com site unsuccessfully (waiting for a long time):
$ src/dillo paths: creating directory /Users/farivar2/.dillo. paths: Cannot open file '/Users/farivar2/.dillo/dillorc' paths: Using /usr/local/etc/dillo/dillorc paths: Cannot open file '/Users/farivar2/.dillo/keysrc' paths: Using /usr/local/etc/dillo/keysrc dillo_dns_init: Here we go! (threaded) Cookies: Created file: /Users/farivar2/.dillo/cookiesrc Disabling cookies. Nav_open_url: new url='about:splash' Nav_open_url: new url='http://www.yahoo.com' Dns_server [0]: www.yahoo.com is 209.191.122.70 69.147.125.65 67.195.160.76 Connecting to 209.191.122.70
and it almost hangs here. During this time the CPU utilization hovers around 134% (on a dual core machine), with 3 threads and 48MB of memory usage.
Is this behavior expected? Perhaps it's related to the warnings above? My guess is that it's either a DNS problem or an HTTP connection problem, resulting into a time-out case.
The warnings are just the compiler noting ambiguous syntax; they shouldn't affect the compilation beyond that. It could be in the DNS or HTTP code. It could also be FLTK. After you send an HTTP request, Dillo uses some FLTK functions to watch the socket for activity. I had a similar problem when I did the Windows port, and it turns out it wasn't Dillo, but buggy and broken FLTK code.
P.S.3 Are there reference rendering snapshots available? The Yahoo's web site and even Google's both render in a strange way (similar to the way links2 renders them). In fact the only website that I could get to render correctly is dillo.org (when it opens, other times it just decides not to open even after 5 minutes of waiting).
That's normal. Dillo still has extremely limited HTML support, so most pages do look rather funny (and it doesn't help that most sites don't recognize Dillo's user agent). A lot of sites, including Google, render better with a Mozilla/4.0 user agent. I actually have the Windows port default to "Mozilla/4.0 (compatible; Dillo 2.2)" for that reason. Cheers, ~Benjamin