Memory leak in Vue.js server-side when using "computed"

[freeozyl80]

Version

vue@2.2.3

Reproduction link

https://github.com/freeozyl80/vue-memory-leak

Steps to reproduce

1. use Vue Server Render (renderToString);
2. the vm in server has "computed" which define a test function without return.(yes ,this step is incorrect, just throw error and pause is ok, but then memory leak happend)
3. memory leak happend.

What is expected?

throw error and pause

What is actually happening?

the vonde is going to run and create, but not destroyed and exit.
In heap snapshots, i found the vue$2 has created almost 4538

---

just look in 'https://github.com/freeozyl80/vue-memory-leak'

[HerringtonDarkholme]

Hi, I have cloned your repository. Wrapping your code in a while (true) statement does not incur out of memory error. This probably means nothing wrong with library code.

Note the memory consumption in your snapshot is under 200MB, which is fairly a low work load for server code. So it is reasonable V8 does not reclaim these memory.

Can you provide more information?

[freeozyl80]

i tried use setInterval， interval of 20 ms. when i run in the server, the memory used by it is increasing



by the way, 200MB is small number, but this happened on the production enviroment when the request almost 30millon per day, fortuneately, i found the reason and made the "computed"'s function correctly. but after that, i wonder why it happend?
by the way, thanks for help

[HerringtonDarkholme]

Please update your code to illustrate the problem.

[freeozyl80]

alreay updated

[HerringtonDarkholme]

Ok, I reproduced it. And commenting out throw new Error does keep memory low.

[HerringtonDarkholme]

Reproducible in browser.

var timer = setInterval(function() {
    const vm = new Vue({
        computed: {
            "test": function() {
                throw 'erro happened';
            }
        }
    });
    try {
        vm.test
    } catch(e) {
    }

}, 1);