Fix memory leaks in libadblockplus

src/FilterEngine.cpp

Index: src/FilterEngine.cpp
===================================================================
--- a/src/FilterEngine.cpp
+++ b/src/FilterEngine.cpp
@@ -233,6 +233,7 @@
   JsValueList params;
   params.push_back(jsEngine->NewValue(domain));
   JsValueList result = func->Call(params)->AsList();
+  jsEngine->Gc();

[Wladimir Palant, 2013/10/08 08:12:19]

This is a really bad idea, it will cause unnecessary delays. Embedders are only
supposed to call V8::IdleNotification() when they are actually idle.

As it is now, the Gc() method is only useful for testing. We can turn it into a
proper wrapper for V8::IdleNotification() - only calling V8::IdleNotification()
once and returning its return value, but with an additional lock to make sure no
JS code is running. However, we would actually need to call that in the
application using libadblockplus (in the message loop or its equivalent) because
otherwise we cannot know when that application is idle. Not quite easy but worth
looking into.

[Felix Dahlke, 2013/10/10 08:36:26]

I don't think we should look into this at this point. High memory usage is what
we get for using garbage collection to begin with, it's an issue we have on each
and every platform. The only real way to fix this is to put energy into avoiding
GC in the core code, which is what ChimeraScript would address.

I doubt that, once we have that, using v8::IdleNotification properly will gain
us much.

   std::vector<std::string> selectors;
   for (JsValueList::iterator it = result.begin(); it != result.end(); ++it)
     selectors.push_back((*it)->AsString());