May 2011 - Dillo-dev - lists.mailman3.com

Connection problems on Mac OS X 10.6.7

by obeythepenguin＠gmail.com

On Fri, 27 May 2011 13:38:43 -0400, reza farivar <rf.opensource(a)gmail.com> wrote: > Yes, Here's the result. I tried it a couple of times, and this looks like > the culprit: > > #13 0x000000010007d373 in do_queued_events () at style.hh:554 > #14 0x000000010007ffa0 in fl_mac_flush_and_wait () at style.hh:554 > #15 0x0000000100083c6f in Fl::run () at style.hh:554 > > Those three lines are consistent everytime I break in GDB. The more > detailed > ones are different of course. Here's one, just in case: > > #0 0x00007fff87967dc5 in tiny_malloc_from_free_list () > #1 0x00007fff87966fdd in szone_malloc_should_clear () > #2 0x00007fff8799d32b in szone_memalign () > #3 0x00007fff879a46eb in malloc_zone_memalign () > #4 0x00007fff87376608 in CFSortIndexes () > #5 0x00007fff87376480 in CFQSortArray () > #6 0x00007fff87386ad2 in __CFRunLoopDoObservers () > #7 0x00007fff87361da4 in CFRunLoopRunSpecific () > #8 0x00007fff842457ee in RunCurrentEventLoopInMode () > #9 0x00007fff842455f3 in ReceiveNextEventCommon () > #10 0x00007fff842454ac in BlockUntilNextEventMatchingListInMode () > #11 0x00007fff85739e64 in _DPSNextEvent () > #12 0x00007fff857397a9 in -[NSApplication > nextEventMatchingMask:untilDate:inMode:dequeue:] () > #13 0x000000010007d373 in do_queued_events () at style.hh:554 > #14 0x000000010007ffa0 in fl_mac_flush_and_wait () at style.hh:554 > #15 0x0000000100083c6f in Fl::run () at style.hh:554 > #16 0x0000000100003a85 in main (argc=1, argv=0x7fff5fbff828) at > dillo.cc:431 I did a bit more looking. Here's style.hh: http://hg.dillo.org/dillo_port1.3/file/b24e8b62bef3/dw/style.hh Line 554 of style.hh is Tooltip (const char *text): TooltipAttrs(text) { refCount = 0; } Then I found this recent thread on FLTK's mailing list: http://comments.gmane.org/gmane.comp.lib.fltk.general/23464 It seems kind of far-fetched, but this leads me to think there's something going on with tooltips -- some bug in the code might be corrupting memory or something. Does adding "show_tooltip=NO" to your dillorc have any effect? ~Benjamin

May 27, 2011

Connection problems on Mac OS X 10.6.7

by obeythepenguin＠gmail.com

On Fri, 27 May 2011 13:38:43 -0400, reza farivar <rf.opensource(a)gmail.com> wrote: > Yes. Well, the only plugin I could see is the save button on the panel, > and > it can successfully navigate the filesystem and save a page correctly. That one isn't a plugin, actually. Does the bookmarks button work? (Dillo's plugins right now are bookmarks, cookies, downloads, view source, and data/file/ftp/https URIs. They're not Flash-type graphical plugins, but things that really should be built into the browser.) > Yes, Here's the result. I tried it a couple of times, and this looks like > the culprit: > > #13 0x000000010007d373 in do_queued_events () at style.hh:554 > #14 0x000000010007ffa0 in fl_mac_flush_and_wait () at style.hh:554 > #15 0x0000000100083c6f in Fl::run () at style.hh:554 > > Those three lines are consistent everytime I break in GDB. The more > detailed > ones are different of course. Here's one, just in case: > > #0 0x00007fff87967dc5 in tiny_malloc_from_free_list () > #1 0x00007fff87966fdd in szone_malloc_should_clear () > #2 0x00007fff8799d32b in szone_memalign () > #3 0x00007fff879a46eb in malloc_zone_memalign () > #4 0x00007fff87376608 in CFSortIndexes () > #5 0x00007fff87376480 in CFQSortArray () > #6 0x00007fff87386ad2 in __CFRunLoopDoObservers () > #7 0x00007fff87361da4 in CFRunLoopRunSpecific () > #8 0x00007fff842457ee in RunCurrentEventLoopInMode () > #9 0x00007fff842455f3 in ReceiveNextEventCommon () > #10 0x00007fff842454ac in BlockUntilNextEventMatchingListInMode () > #11 0x00007fff85739e64 in _DPSNextEvent () > #12 0x00007fff857397a9 in -[NSApplication > nextEventMatchingMask:untilDate:inMode:dequeue:] () > #13 0x000000010007d373 in do_queued_events () at style.hh:554 > #14 0x000000010007ffa0 in fl_mac_flush_and_wait () at style.hh:554 > #15 0x0000000100083c6f in Fl::run () at style.hh:554 > #16 0x0000000100003a85 in main (argc=1, argv=0x7fff5fbff828) at > dillo.cc:431 It looks like the problem's somewhere in FLTK. I'll take a look and see what I can find. Cheers, ~Benjamin

May 27, 2011

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

On Fri, May 27, 2011 at 10:28 AM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > On Thu, May 26, 2011 at 03:42:04PM -0500, reza farivar wrote: > > On Thu, May 26, 2011 at 3:18 PM, Johannes Hofmann > > > > > [...] > > > Did you take special care to compile fltk-1.3 with X11 backend? > > > If not, you might run the dillo as native Cocoa application. > > > In that case you were more successful then me. > > > For me dillo with Cocoa-fltk starts, but does not load any remote > > > pages. There seem to be severe issues with the way fltk handles events > > > in the Cocoa case. > > > > > > > Hmm, maybe I should try recompiling fltk with X11 backend...But my > current > > native version is so close to working with no problems... > > Yes, it's amazing how close it is from working native. > Are plugins working OK? (e.g. can you browse the filesystem?) > Yes. Well, the only plugin I could see is the save button on the panel, and it can successfully navigate the filesystem and save a page correctly. > > Do you know how to use gdb? > It would be great to know in what functions the busy wait happens. > It could be a timeout or anything. For this: gdb ./dillo > <when locked on high CPU usage, hit Ctrl-c> bt > Yes, Here's the result. I tried it a couple of times, and this looks like the culprit: #13 0x000000010007d373 in do_queued_events () at style.hh:554 #14 0x000000010007ffa0 in fl_mac_flush_and_wait () at style.hh:554 #15 0x0000000100083c6f in Fl::run () at style.hh:554 Those three lines are consistent everytime I break in GDB. The more detailed ones are different of course. Here's one, just in case: #0 0x00007fff87967dc5 in tiny_malloc_from_free_list () #1 0x00007fff87966fdd in szone_malloc_should_clear () #2 0x00007fff8799d32b in szone_memalign () #3 0x00007fff879a46eb in malloc_zone_memalign () #4 0x00007fff87376608 in CFSortIndexes () #5 0x00007fff87376480 in CFQSortArray () #6 0x00007fff87386ad2 in __CFRunLoopDoObservers () #7 0x00007fff87361da4 in CFRunLoopRunSpecific () #8 0x00007fff842457ee in RunCurrentEventLoopInMode () #9 0x00007fff842455f3 in ReceiveNextEventCommon () #10 0x00007fff842454ac in BlockUntilNextEventMatchingListInMode () #11 0x00007fff85739e64 in _DPSNextEvent () #12 0x00007fff857397a9 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] () #13 0x000000010007d373 in do_queued_events () at style.hh:554 #14 0x000000010007ffa0 in fl_mac_flush_and_wait () at style.hh:554 #15 0x0000000100083c6f in Fl::run () at style.hh:554 #16 0x0000000100003a85 in main (argc=1, argv=0x7fff5fbff828) at dillo.cc:431 -Reza > This can hint us on what may be happening. > > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

May 27, 2011

Connection problems on Mac OS X 10.6.7

by jcid＠dillo.org

On Thu, May 26, 2011 at 03:42:04PM -0500, reza farivar wrote: > On Thu, May 26, 2011 at 3:18 PM, Johannes Hofmann > > > [...] > > Did you take special care to compile fltk-1.3 with X11 backend? > > If not, you might run the dillo as native Cocoa application. > > In that case you were more successful then me. > > For me dillo with Cocoa-fltk starts, but does not load any remote > > pages. There seem to be severe issues with the way fltk handles events > > in the Cocoa case. > > > > Hmm, maybe I should try recompiling fltk with X11 backend...But my current > native version is so close to working with no problems... Yes, it's amazing how close it is from working native. Are plugins working OK? (e.g. can you browse the filesystem?) Do you know how to use gdb? It would be great to know in what functions the busy wait happens. It could be a timeout or anything. For this: gdb ./dillo <when locked on high CPU usage, hit Ctrl-c> bt This can hint us on what may be happening. -- Cheers Jorge.-

May 27, 2011

What's currently broken in... (Re: [Dillo-dev] 1.3 port)

by jcid＠dillo.org

On Wed, May 25, 2011 at 04:37:33PM -0800, Roger wrote: > > On Wed, May 25, 2011 at 03:13:54PM +0000, corvid wrote: > >Jorge wrote: > >> On Sun, May 15, 2011 at 09:04:43PM +0200, Johannes Hofmann wrote: > >> > > >> > - There is a tab title even if there is only one tab. > >> > >> FYI, I'm testing a patch that does this. It uses a trick to > >> receive events on a hidden tabbar and is designed so it's easy to > >> set permanent tab buttons too (i.e. as now). > >> > >> Quick poll: What's your preferred mode? > > > >I prefer that the tab bar goes away when there's only one tab. > > > >I will feel surprise if anyone wants to have it visible when > >there's only one tab. > > Well, be surprised. I like to see a tab even though there's no more then one > visible. Reason being, Firefox tends (or tended) to resize the webpage and > toolbars when migrating from one to more then one tabs, it boggled my mind > when comprehending, "Now what changed??" It would take a few seconds to regain > field of view, etc. (No glasses, 20/20 here, no drugs or alcohol, etc) > > But I'm guessing with FLTK, it won't make such vast changes when going from > tabs to no tabs. Also, the Title of the webpage is usually kept within the > tab. <shrugs, for what it's worth> Fair enough. With Dillo you won't have such delays. Please test the just committed patch! -- Cheers Jorge.-

May 27, 2011

Connection problems on Mac OS X 10.6.7

by corvid＠lavabit.com

reza wrote: > I also have similar problems with > missing images. Mostly when there is an image that has a link associated > with it, the images don't load and only an empty frame is displayed. If I > click inside the frame, it loads the image. The second click takes me to the > target URL. In dillorc, you might try filter_auto_requests=allow_all

May 26, 2011

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

On Thu, May 26, 2011 at 3:18 PM, Johannes Hofmann <Johannes.Hofmann(a)gmx.de>wrote: > > The good news is that Dillo runs. It also seems to eventually connect to > > websites, which is good news too. > > I assume you compiled fltk with X11 backend. I'm also using this > setup and it works more or less fine for me. > For some sites though I see missing images or stylesheets. > I didn't find time to investigate this further. > > No, I'm running it native on Mac OS X. I also have similar problems with missing images. Mostly when there is an image that has a link associated with it, the images don't load and only an empty frame is displayed. If I click inside the frame, it loads the image. The second click takes me to the target URL. > > > > 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): > > I think logging the exact return codes and errno values of the > network related syscalls might give us a clue why things go bad > sometimes. How would I do that? Dillo definitely doesn't print them to the terminal from which I run it. I don't have anything from dillo on the console either (console looks at console.log, system.log, ~/Library/Logs, /Library/Logs, /var/logs). > > 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. > > Ouch. I didn't see that yet. > > It's definitely there, look at my other mail and the consistent scenario I can make. > > > > 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. > > It's certainly not expected. > > > > > P.S. Sometimes it seems if I open another tab and enter another address > it > > will help the first tab to load, but I can't get it to consistently act > like > > that. Other times, it seems a tab can get stuck waiting for the host and > can > > never load the page. It also seems adding http:// to the beggining of > > addresses help some times, but not consistently. > > > > P.S.2 I checked my network connection with my other browser (chrome) and > it > > has no problem connecting the mentioned websites. > > > > 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). > > Well, that's life with dillo :) > But we are working on improving compatibility. > > > > > P.S.4 Jorge's instructions to compile dillo-1.3 for Mac OS X are as > follows: > > > > 1.- <install fltk-1.3-rc5 from fltk.org> > > Did you take special care to compile fltk-1.3 with X11 backend? > If not, you might run the dillo as native Cocoa application. > In that case you were more successful then me. > For me dillo with Cocoa-fltk starts, but does not load any remote > pages. There seem to be severe issues with the way fltk handles events > in the Cocoa case. > Hmm, maybe I should try recompiling fltk with X11 backend...But my current native version is so close to working with no problems... > > Cheers, > Johannes > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

May 26, 2011

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

On Thu, May 26, 2011 at 11:15 AM, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > Hi, > > On Thu, May 26, 2011 at 02:34:06AM -0500, reza farivar wrote: > > > > 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): > > > > 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. > > The busy wait is a sign that something went really wrong. > If it was a slow DNS, polling would not bump CPU usage. > > So after installing the latest version of dillo (and disabling threaded DNS) I have no warnings but the problems still remain. I can consistently make the following scenario happen: After starting dillo, I open a new tab and enter a random website URL. Dillo gets into the busy wait loop (133% CPU usage, 3 threads) and doesn't load the page even after 10 minutes of waiting. Then I open another tab and enter another website (www.yahoo.com) and this makes both tabs to load their contents immediately. In general I never saw a connection problem when opening a link in a currently opened page. The problem always happens when entering a page URL manually in the address bar. > > > > Is this behavior expected? > > Not at all. > > > Perhaps it's related to the warnings above? > > Hardly. > > > My > > guess is that it's either a DNS problem or an HTTP connection problem, > > resulting into a time-out case. > > A couple of years ago I tried dillo-2.x in a Mac (FLTK2), and > it mainly worked (without the delays you describe). I did compile > it with the X server stuff. I don't know whether it is possible > to compile it natively. > > In what mode are you testing? (I ask because you said you > couldn't compile dillo-2.x). > > I am not running it with the X server. I think I have fltk1.3 compiled as native cocoa, the X11 server never opens up when running dillo, while other X11 apps (say links2) load it up. So I'm pretty sure I'm running it native. > > P.S. Sometimes it seems if I open another tab and enter another address > it > > will help the first tab to load, but I can't get it to consistently act > like > > that. Other times, it seems a tab can get stuck waiting for the host and > can > > never load the page. It also seems adding http:// to the beggining of > > addresses help some times, but not consistently. > > No. That's coincidence. > Maybe there's a timing/sequence problem with the socket > connection. If I only had a Mac here to try... > Please see the scenario described above. > > > > P.S.2 I checked my network connection with my other browser (chrome) and > it > > has no problem connecting the mentioned websites. > > If the other browser gets a quick DNS answer, then the problem > is elsewhere. > > > 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). > > Dillo doesn't have support for "floating elements" yet. The web > has become full of them because of slow rendering of tables. > Well, we're supposed to work on it in the near future. For the > meanwhile, you'll see weird "unrolled" pages. > That good to hear. It seems you guys are now focused on this port to 1.3 for the time being? Is the floating elements next in line? Thanks, Reza > > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

May 26, 2011

Connection problems on Mac OS X 10.6.7

by Johannes.Hofmann＠gmx.de

Welcome, On Thu, May 26, 2011 at 02:34:06AM -0500, reza farivar 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: > > $ make|grep : > http.c: In function ?Http_connect_queued_sockets?: > http.c:177: warning: cast from pointer to integer of different size > dialog.cc: In function ?int a_Dialog_choice5(const char*, const char*, const > char*, const char*, const char*, const char*)?: > dialog.cc:177: warning: suggest a space before ?;? or explicit braces around > empty body in ?for? statement > make[2]: Nothing to be done for `all'. > make[2]: Nothing to be done for `all-am'. > > The good news is that Dillo runs. It also seems to eventually connect to > websites, which is good news too. I assume you compiled fltk with X11 backend. I'm also using this setup and it works more or less fine for me. For some sites though I see missing images or stylesheets. I didn't find time to investigate this further. > > 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): I think logging the exact return codes and errno values of the network related syscalls might give us a clue why things go bad sometimes. > > $ 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. Ouch. I didn't see that yet. > > 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. It's certainly not expected. > > P.S. Sometimes it seems if I open another tab and enter another address it > will help the first tab to load, but I can't get it to consistently act like > that. Other times, it seems a tab can get stuck waiting for the host and can > never load the page. It also seems adding http:// to the beggining of > addresses help some times, but not consistently. > > P.S.2 I checked my network connection with my other browser (chrome) and it > has no problem connecting the mentioned websites. > > 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). Well, that's life with dillo :) But we are working on improving compatibility. > > P.S.4 Jorge's instructions to compile dillo-1.3 for Mac OS X are as follows: > > 1.- <install fltk-1.3-rc5 from fltk.org> Did you take special care to compile fltk-1.3 with X11 backend? If not, you might run the dillo as native Cocoa application. In that case you were more successful then me. For me dillo with Cocoa-fltk starts, but does not load any remote pages. There seem to be severe issues with the way fltk handles events in the Cocoa case. Cheers, Johannes

May 26, 2011

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

On Thu, May 26, 2011 at 10:46 AM, corvid <corvid(a)lavabit.com> wrote: > reza wrote: > > 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. > > Just out of curiosity, does anything change if you configure with > --disable-threaded-dns? > > I tried it, it feels it might have become better, but the problems still remain. If you don't want a touchy feely answer, then no, disable-threaded-dns didn't fix the problem. > I tried valgrind's helgrind tool a couple of weeks ago, and it complains > and complains about threads, but I didn't know whether any of it had > any significance. > > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

May 26, 2011