edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Error Legs
Date: Fri, 07 Feb 2014 10:23:05 -0800	[thread overview]
Message-ID: <87vbwqg4ty.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140107125753.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 07 Feb 2014 12:57:53 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> I pushed a small change to use the symbol and message we already had for this

Oh, right.  You forgot to modify jsdom.cpp though.
Fixed and pushed.

> My gut tells me the segfaults might come from somewhere else.

Here's a transcript.
This is with the 4 meg size for JS_NewRuntime and the new change to my_ErrorReporter.

Script started on Fri 07 Feb 2014 10:15:32 AM PST
./edbrowse http://www.youtube.com
..
230809
13578
/Popu
* {Thumbnail Popular on YouTube} 
g
.....
508101
JavaScript failure
chris@mushroom: /files/cmb-files/repos/edbrowse/src $ exit
exit

Script done on Fri 07 Feb 2014 10:15:55 AM PST

So it is failing with out-of-memory in this case.  I'm sure youtube is a
very JS-intensive site, but could there be another reason for the memory
exaustion?  I don't know.

-- Chris

  reply	other threads:[~2014-02-07 18:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 17:57 Karl Dahlke
2014-02-07 18:23 ` Chris Brannon [this message]
2014-02-09 10:45   ` Adam Thompson
2014-02-09 11:10     ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2014-02-09 14:48 Karl Dahlke
2014-02-09 15:21 ` Adam Thompson
2014-02-09 14:18 Karl Dahlke
2014-02-09 15:13 ` Adam Thompson
2014-02-07 20:06 Karl Dahlke
2014-02-07 19:37 Karl Dahlke
2014-02-07 19:55 ` Chris Brannon
2014-02-07 14:01 Karl Dahlke
2014-02-07 15:05 ` Chris Brannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vbwqg4ty.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).