Adam Thompson <[email protected]> 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
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev

Reply via email to