[Webkit-unassigned] [Bug 24615] JavascriptCore leaks when creating and releasing context groups in a tight loop

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=24615





--- Comment #14 from Scott <bugs.webkit.org at scottdavies.net>  2013-06-01 11:19:19 PST ---
(In reply to comment #13)

> Hmm, I'm a little confused. Nightlies shouldn't have to be built/compiled. You just download them from http://nightly.webkit.org and the new JavaScriptCore.framework should be in /path/to/downloaded/WebKit.app/Contents/Frameworks/10.8/.

I'm investigating the feasibility of using JavaScriptCore as a general-purpose JavaScript engine inside my codebase without making a complete mess of my overall build system or making things too platform-specific, so I've been downloading source distributions and playing with those instead of prebuilt OS X-specific dmgs. (Partly for yuks, I wrote a script that agglomerates the JavaScriptCore source files into a single C++ file that compiles with minimal dependencies, although some of those "source files" are derived sources that were generated during the usual WebKit build process.  It's 12MB, takes about a minute to compile, and probably isn't particularly platform-independent yet, but so far it seems to compile and run on OS X without actually using any OS X frameworks.)

Since I'm thinking about using it in servers, memory leaks in JSC would be Bad.  I encountered at least two different memory leaks in the preinstalled system JSC framework right off the bat (one of them being the one exercised here), so I was about to give up on JSC and look into maybe using SpiderMonkey instead, but both of those leaks seem to be plugged in the nightly I just built, so I guess I'll play with JSC some more.

> As for dealing with WebKitSystemInterface.h related build errors, http://www.webkit.org/building/build.html should help you with these issues as Mark Rowe mentioned above.

Yeah, I'd hastily misread that page a while ago and not realized that build-webkit was in fact what I wanted for UNIX command-line builds...so I'd tried just running "make" in the top-level directory, and that managed to lull me into thinking it was the right thing to do since it at least got as far as building JSC correctly before crapping out on NetscapePluginHostManager.mm.  build-webkit does in fact seem to build the whole thing successfully, though.  (At least on my laptop.  It immediately fails on my desktop, but that's another story...looks like I've got an extra, incompatible version of QT or perl or something installed on the desktop.  Whee.  Well, I guess that's one thing an "All of JSC in one C++ file" agglomeration might be good for...)

Anyhow, thanks!

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.