On Fri, May 14, 2010 at 08:51:33AM -0400, Jorge Arellano Cid wrote:
On Wed, May 12, 2010 at 03:44:50PM -0400, Matthew Craig wrote:
Thanks for your response. Sorry that I am reluctant to join any mailing lists. The Lemote laptop has alot of memory: 1GB and 2.7GB swap. I am running GNOME without memory problems, and usage rarely rises over 50% ... I am reluctant to presume Dillo is using all the memory up, but I have been watching it today.
Browsing to that website when Dillo is started fresh does indeed cause an immediate crash.
OK, that eliminates the memory shortage thesis...
mtc@freedomincluded:~$ dillo -g 999x666 http://uaddit.com/discussions/showthread.php?t=5931 paths: Cannot open file '/home/mtc/.dillo/keysrc' paths: Using /usr/local/etc/dillo/keysrc dillo_dns_init: Here we go! (threaded) Disabling cookies. Nav_open_url: new url='http://uaddit.com/discussions/showthread.php?t=5931' Dns_server [0]: uaddit.com is 72.44.80.46 Connecting to 72.44.80.46 CssParser::parseImport(): @import clientscript/vbulletin_css/style-01a90dc0-00011.css terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted
Please start dillo, disable css (tools button) and load the page. If it doesn't crash after the page loads, enable css again and see what happens (this is to check in what part of dillo the allocation problem is and to discard a race condition between css and html rendering).
This bug is very interesting (probably there's something uninitialized in dillo or outside of it). I'll check with valgrind.
Can someone else reproduce this bug?
Works fine for me. Are there any process limits set in your environmen (ulimit -a)? Cheers, Johannes