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] js progress update
Date: Fri, 17 Jan 2014 10:42:25 -0800	[thread overview]
Message-ID: <87d2jqv4a6.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140117120949.GC21779@spoons.adamthompson.me.uk> (Adam Thompson's message of "Fri, 17 Jan 2014 12:09:49 +0000")

Adam Thompson <arthompson1990@gmail.com> writes:

> Yeah, particularly if using a debug build of smjs.

Also -- and you may have already discovered this -- it seems that you
need openssl built with -DPURIFY in CFLAGS to make running under
valgrind effective.  Otherwise, you get a bunch of spurious
"uninitialized value" errors caused by openssl.  I've started running
under valgrind.  So far, the only memory leak I've found is not
JS-related at all; it's in htmlAttrVal.  I believe it's caused by
returning NULL / 0 in the middle of the function without calling nzFree
on a now-unreachable allocated string.
So I'll keep on testing for other leaks.

PS.  I managed to crash the latest yesterday, running under mozjs 24,
while browsing netflix.com.  I couldn't repeat it, though.

-- Chris

  reply	other threads:[~2014-01-17 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 11:05 Karl Dahlke
2014-01-08 12:40 ` Adam Thompson
2014-01-14 20:43   ` Chris Brannon
2014-01-14 21:27     ` Adam Thompson
2014-01-14 22:17       ` Chris Brannon
2014-01-17 12:09         ` Adam Thompson
2014-01-17 18:42           ` Chris Brannon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-07 12:08 Adam Thompson
2014-01-07 12:10 ` [Edbrowse-dev] js progress update1 Adam Thompson
2014-01-08 10:03   ` [Edbrowse-dev] js progress update Adam Thompson

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=87d2jqv4a6.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).