Yes, the memory leak in this code isn't visible as it appears.
I observed the memory leak when I ran the "top" command. But when I
commented out the call to "NewInstance()", there wasn't any growth in
memory (which is obvious because there's nothing being created and passed
onto the JS world).
On Tue, Apr 18, 2017 at 9:31 AM, Gautham B A
wrote:
> Thank you Ben.
> Yes, there's a try_catch.HasCaught() before running the script in order to
> prevent the process from exiting.
> Here's the code that will cause the script to run -
> int SendUpdate(std::string
Thank you Ben.
Yes, there's a try_catch.HasCaught() before running the script in order to
prevent the process from exiting.
Here's the code that will cause the script to run -
int SendUpdate(std::string value, std::string meta,
std::string doc_type) {
v8::Locker
On Tue, Apr 18, 2017 at 7:32 AM, Gautham B A
wrote:
> Hi all,
>
> I'm observing a memory leak when the script crashes at runtime. Here the
> JavaScript code (made to crash on purpose by throwing Exception).
> var res = new N1qlQuery('SELECT * FROM `sample`');
> throw