- Dillo-dev - lists.mailman3.com

Re: dillo mysteriously freezes

by dennisn＠dennisn.dyndns.org

On Thu, 17 Jun 2010 21:37:23 +0000, corvid wrote: > Jeremy wrote: > > On Thu, Jun 17, 2010 at 02:42:19PM -0400, Dennis Nezic wrote: > > > > > Interesting. It appears that I only get these freezes when I > > > have cookies enabled. If I set my cookiesrc file back to > > > "DEFAULT DENY" (with no "hostname ACCEPT" afterwards), I no > > > longer get the freezes. > > > > That's useful confirmation that it's a cookies problem. > > Does the DPI stuff work otherwise? Bookmarks, https:, file:... Bah. It looks like all the dpi stuff is commonly affected. I tried browsing locally with file:// and the same thing occurred. It also did unfreeze after about a minute. > > > > > ps -ef | grep dpi doesn't show anything interesting: > > > 1533 1 0 14:31 ? 00:00:00 dpid > > > 1534 1533 0 14:31 ? > > > 00:00:00 /usr/lib64/dillo/dpi/cookies/cookies.dpi > > > > It shows that neither the DPI daemon or the cookies DPI have > > crashed, which is something. I wonder what the cookies DPI is > > doing? Does anyone know how to attach gdb to the cookies DPI > > and see where it's at? > > gdb /usr/lib64/dillo/dpi/cookies/cookies.dpi 1534 > or something along those lines...

June 18, 2010

Re: dillo mysteriously freezes

by corvid＠lavabit.com

Jeremy wrote: > On Thu, Jun 17, 2010 at 02:42:19PM -0400, Dennis Nezic wrote: > > > Interesting. It appears that I only get these freezes when I have > > cookies enabled. If I set my cookiesrc file back to "DEFAULT DENY" > > (with no "hostname ACCEPT" afterwards), I no longer get the freezes. > > That's useful confirmation that it's a cookies problem. Does the DPI stuff work otherwise? Bookmarks, https:, file:... > > ps -ef | grep dpi doesn't show anything interesting: > > 1533 1 0 14:31 ? 00:00:00 dpid > > 1534 1533 0 14:31 ? 00:00:00 /usr/lib64/dillo/dpi/cookies/cookies.dpi > > It shows that neither the DPI daemon or the cookies DPI have crashed, > which is something. I wonder what the cookies DPI is doing? Does > anyone know how to attach gdb to the cookies DPI and see where it's > at? gdb /usr/lib64/dillo/dpi/cookies/cookies.dpi 1534 or something along those lines...

June 17, 2010

Re: dillo mysteriously freezes

by onepoint＠starurchin.org

On Thu, Jun 17, 2010 at 02:42:19PM -0400, Dennis Nezic wrote: > Interesting. It appears that I only get these freezes when I have > cookies enabled. If I set my cookiesrc file back to "DEFAULT DENY" > (with no "hostname ACCEPT" afterwards), I no longer get the freezes. That's useful confirmation that it's a cookies problem. > ps -ef | grep dpi doesn't show anything interesting: > 1533 1 0 14:31 ? 00:00:00 dpid > 1534 1533 0 14:31 ? 00:00:00 /usr/lib64/dillo/dpi/cookies/cookies.dpi It shows that neither the DPI daemon or the cookies DPI have crashed, which is something. I wonder what the cookies DPI is doing? Does anyone know how to attach gdb to the cookies DPI and see where it's at? Regards, Jeremy Henty

June 17, 2010

Re: dillo mysteriously freezes

by dennisn＠dennisn.dyndns.org

On Thu, 17 Jun 2010 19:03:32 +0100, Jeremy Henty wrote: > On Thu, Jun 17, 2010 at 01:36:47PM -0400, Dennis Nezic wrote: > > > (gdb) bt > > #0 0x00007f3cca17089d in connect () from /lib/libpthread.so.0 > > #1 0x000000000044227e in Dpi_connect_socket () > > #2 0x0000000000442f6f in a_Dpi_send_blocking_cmd () > > #3 0x0000000000411115 in a_Cookies_get_query () > > #4 0x000000000044098d in a_Http_make_query_str () > > #5 0x0000000000441481 in Http_connect_queued_sockets () > > #6 0x00000000004375da in Dns_timeout_client () > > #7 0x00007f3ccac8c4cf in fltk::wait () > > #from /usr/lib64/fltk/libfltk2.so 8 0x00007f3ccac8c595 in > > #fltk::run () from /usr/lib64/fltk/libfltk2.so 9 > > #0x000000000040af23 in main () > > It looks as though Dillo is waiting for an answer from the cookies DPI > and not getting one. What is the output of "ps -ef | grep dpi"? It > would also be useful if you could save the output of Dillo to a log > file and send it (it's unlikely to be a large file if Dillo hangs > after a few seconds). Interesting. It appears that I only get these freezes when I have cookies enabled. If I set my cookiesrc file back to "DEFAULT DENY" (with no "hostname ACCEPT" afterwards), I no longer get the freezes. ps -ef | grep dpi doesn't show anything interesting: 1533 1 0 14:31 ? 00:00:00 dpid 1534 1533 0 14:31 ? 00:00:00 /usr/lib64/dillo/dpi/cookies/cookies.dpi Sometimes, however, my cpu stalls at 100%, I think caused by dpid, but top only shows 17% from it -- (the rest I assume is some lower level system hook?) -- but this doesn't always happen. Also, I did see dillo unfreeze once, after a few seconds -- but that is rare.

June 17, 2010

Re: dillo mysteriously freezes

by onepoint＠starurchin.org

On Thu, Jun 17, 2010 at 01:36:47PM -0400, Dennis Nezic wrote: > (gdb) bt > #0 0x00007f3cca17089d in connect () from /lib/libpthread.so.0 > #1 0x000000000044227e in Dpi_connect_socket () > #2 0x0000000000442f6f in a_Dpi_send_blocking_cmd () > #3 0x0000000000411115 in a_Cookies_get_query () > #4 0x000000000044098d in a_Http_make_query_str () > #5 0x0000000000441481 in Http_connect_queued_sockets () > #6 0x00000000004375da in Dns_timeout_client () > #7 0x00007f3ccac8c4cf in fltk::wait () from /usr/lib64/fltk/libfltk2.so > #8 0x00007f3ccac8c595 in fltk::run () from /usr/lib64/fltk/libfltk2.so > #9 0x000000000040af23 in main () It looks as though Dillo is waiting for an answer from the cookies DPI and not getting one. What is the output of "ps -ef | grep dpi"? It would also be useful if you could save the output of Dillo to a log file and send it (it's unlikely to be a large file if Dillo hangs after a few seconds). Regards, Jeremy Henty

June 17, 2010

Re: dillo mysteriously freezes

by dennisn＠dennisn.dyndns.org

On Thu, 17 Jun 2010 11:14:43 -0400, Jorge Arellano Cid wrote: > On Thu, Jun 17, 2010 at 09:44:03AM -0400, Dennis Nezic wrote: > > I seem to be experiencing a very nasty bug that breaks my Dillo. A > > few seconds after starting dillo, it "freezes" -- standard-output > > stops, the graphics freeze and never get redrawn (resulting in those > > psychodelic effects of moving windows over a non-redrawing window). > > My dillo window then doesn't respond to my window manager's "close" > > events, and I have to manually kill it. > > > > I can't give you the exact steps to reproduce it -- sometimes it's > > like this immediately after starting ... sometimes it magically > > starts to happen a few seconds afterwards -- possibly after I click > > on a link. > > > > dillo-2.2 > > fltk-2_pre7513 (I also tried with earlier versions (6970)) > > > > Ideas? > > gdb dillo > <dillo freezes somewhere here> > ctrl-c > bt > > And send us the gdb backtrace. (gdb) bt #0 0x00007f3cca17089d in connect () from /lib/libpthread.so.0 #1 0x000000000044227e in Dpi_connect_socket () #2 0x0000000000442f6f in a_Dpi_send_blocking_cmd () #3 0x0000000000411115 in a_Cookies_get_query () #4 0x000000000044098d in a_Http_make_query_str () #5 0x0000000000441481 in Http_connect_queued_sockets () #6 0x00000000004375da in Dns_timeout_client () #7 0x00007f3ccac8c4cf in fltk::wait () from /usr/lib64/fltk/libfltk2.so #8 0x00007f3ccac8c595 in fltk::run () from /usr/lib64/fltk/libfltk2.so #9 0x000000000040af23 in main () I don't know if this helps -- but that's the bt for dillo after I ctrl-c, after the graphics/ui becomes unresponsive.

June 17, 2010

dillo mysteriously freezes

by jcid＠dillo.org

On Thu, Jun 17, 2010 at 09:44:03AM -0400, Dennis Nezic wrote: > I seem to be experiencing a very nasty bug that breaks my Dillo. A few > seconds after starting dillo, it "freezes" -- standard-output stops, > the graphics freeze and never get redrawn (resulting in those > psychodelic effects of moving windows over a non-redrawing window). My > dillo window then doesn't respond to my window manager's "close" > events, and I have to manually kill it. > > I can't give you the exact steps to reproduce it -- sometimes it's like > this immediately after starting ... sometimes it magically starts to > happen a few seconds afterwards -- possibly after I click on a link. > > dillo-2.2 > fltk-2_pre7513 (I also tried with earlier versions (6970)) > > Ideas? gdb dillo <dillo freezes somewhere here> ctrl-c bt And send us the gdb backtrace. -- Cheers Jorge.-

June 17, 2010

dillo mysteriously freezes

by dennisn＠dennisn.dyndns.org

I seem to be experiencing a very nasty bug that breaks my Dillo. A few seconds after starting dillo, it "freezes" -- standard-output stops, the graphics freeze and never get redrawn (resulting in those psychodelic effects of moving windows over a non-redrawing window). My dillo window then doesn't respond to my window manager's "close" events, and I have to manually kill it. I can't give you the exact steps to reproduce it -- sometimes it's like this immediately after starting ... sometimes it magically starts to happen a few seconds afterwards -- possibly after I click on a link. dillo-2.2 fltk-2_pre7513 (I also tried with earlier versions (6970)) Ideas?

June 17, 2010

Unexplained Dillo Segfault

by rogerx＠sdf.org

On Wed, Jun 16, 2010 at 04:00:49PM +0000, corvid wrote: >rogerx wrote: >> Re-built fltk using "xft", and all seems quiet so far -- no signs of segfault. > >Oh, good good good... OK. Just rambling some thoughts to make sure I have things correct. When I get a chance today, I'll try to open a bug on bugs.gentoo.org concerning this missing runtime depend for a variable font. -- Roger http://rogerx.freeshell.org/

June 16, 2010

Unexplained Dillo Segfault

by corvid＠lavabit.com

rogerx wrote: > On Tue, Jun 15, 2010 at 06:17:11PM +0000, corvid wrote: > >Dillo is set to use DejaVu fonts by default (set in dillorc file), but your > >backtrace showed that fltk is using Font_xlfd.cxx instead of Font_xft.cxx, > >indicating that your fltk was configured with --disable-xft. > >With xft disabled, it's not going to use TTF fonts. > > For those that know this, it's a no brainer -- but obviously I don't as such > easily assumed since I installed Dejavue, it would use those fonts. :-/ Dillo prints out a warning message if it can't load one of the fonts given in dillorc. > Did the debug info (error code) seem kind of brief to you? The "bad font: variable" that fltk2 spits out? Yeah. > >If you don't mind using antialiased fonts, you could reconfigure with xft > >enabled, and recompile, and everything may just magically work. > >If not, and you like bitstream, I'd alias 'fixed' to one of the > >bitstream terminal choices, and alias 'variable' perhaps to one of the > >bitstream charter ones. (And then I think you'd have to run mkfontdir > >afterward.) > > Re-built fltk using "xft", and all seems quiet so far -- no signs of segfault. Oh, good good good... > This definitely seems like fltk cannot be built without xft -- or if without > xft -- user needs to have a variable font installed. Sounds like the package > manager script is missing a depend check. My guess is that "fixed" and "variable" may be standard enough that it's a misconfiguration not to have the aliases present and set to a font that you have, although, yeah, it's a bug in fltk2 not to handle that gracefully. > As far as having the extra eye-candy, I prefer only building/installing stuff > that's needed versus installing a mess of eye candy I don't make much use of. > Hence, the reason why I skipped building "without xft". ;-) Well, it "should" :) 1) not crash 2) print a warning to the terminal if dillo can't use the fonts that it's set to use. In any case, I should update the comments in the fonts section of dillorc to reflect the current state of things. Most/all of the text in that section hasn't been touched since the dillo1 days.

June 16, 2010