This URL reliably segfaults Dillo: http://freethoughtblogs.com/butterfliesandwheels/2014/04/where-will-brandeis... I suspect this is due to a very recent change as for the past few days Dillo has been crashing a lot, which until then hadn't happened in ages. I haven't investigated further. Dillo (current hg tip), Linux 3.13.9, glibc 2.13, gcc 4.5.2 . Regards, Jeremy Henty
On Mo, Apr 14, 2014, Jeremy Henty wrote:
This URL reliably segfaults Dillo:
http://freethoughtblogs.com/butterfliesandwheels/2014/04/where-will-brandeis...
I suspect this is due to a very recent change as for the past few days Dillo has been crashing a lot, which until then hadn't happened in ages. I haven't investigated further.
Dillo (current hg tip), Linux 3.13.9, glibc 2.13, gcc 4.5.2 .
Yes, everything after revision 3613 segfault; you can stick to this if you want to run the development version. (There are no important changes yet after this.) This is part of a couple of changes which I hoped to solve another problem, but which did not serve this purpose, so I'll probably soon revert these changes again. Sebastian
Hi Jeremy, On Mon, Apr 14, 2014 at 07:22:35AM +0100, Jeremy Henty wrote:
This URL reliably segfaults Dillo:
http://freethoughtblogs.com/butterfliesandwheels/2014/04/where-will-brandeis...
I suspect this is due to a very recent change as for the past few days Dillo has been crashing a lot, which until then hadn't happened in ages. I haven't investigated further.
Dillo (current hg tip), Linux 3.13.9, glibc 2.13, gcc 4.5.2 .
Yes, after the dillo-3.0.4 release, the large work on floating elements was merged into the repository, leaving a very unstable and crashy dillo. Users should stick to dillo-3.0.4 in the meantime. IMO, we (developers) need to focus as a team on stabilizing this tree before planning any further enhancements. Only once this goal is met we can return to our usual workflow. -- Cheers Jorge.-
Jorge Arellano Cid wrote:
IMO, we (developers) need to focus as a team on stabilizing this tree before planning any further enhancements. Only once this goal is met we can return to our usual workflow.
Completely agree. It's just like old times! <nostalgia/> :-) Maybe I can update my wrappers to automatically generate tracebacks from core files. Hmm... Regards, Jeremy Henty
I wrote:
This URL reliably segfaults Dillo:
http://freethoughtblogs.com/butterfliesandwheels/2014/04/where-will-brandeis...
In fact as far as I can tell *any* page from freethoughtblogs.com crashes Dillo, which suggests that it is site style that is causing it rather than the content. The page content downloads without any problem and Dillo starts rendering it and downloading images for a few seconds, then crashes. This suggests to me that it is still downloading the CSS and crashes when it tries to style the page. (I run Dillo inside valgrind so everything happens around 30x slower for me. I can clearly see Dillo restyling the page once the CSS has downloaded.) Regards, Jeremy Henty
participants (3)
-
jcid＠dillo.org -
onepoint＠starurchin.org -
sgeerken＠dillo.org