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.

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

I can't reproduce it with valgrind... :-P ...but, from the above output, the last debug message comes from cssparser.cc:1428 and it calls a_Html_load_stylesheet() which should print "NumPendingStyleSheets=1" (html.cc:2985). So, the problem is in this tiny spot. Please run gdb, set a break point in a_Html_load_stylesheet() and follow it carefully step by step until it crashes to know in what line the problem is triggered. -- Cheers Jorge.-