I was wondering how can WebKitTestRunner eat GB's of memory and started checking memory usage with valgrind. I'm not sure yet that this will fix everything but at least this is a pretty trivial memory leak so let's fix it.
Created attachment 168226 [details]
Comment on attachment 168226 [details]
Clearing flags on attachment: 168226
Committed r131065: <http://trac.webkit.org/changeset/131065>
All reviewed patches have been landed. Closing bug.