Devtools tries to serialize whole VNodes

[jsm1003]

Version

4.1.5

Browser and OS info

Chrome 71.0.3578.98/Windows 10

Steps to reproduce

git clone [email protected]:jsm1003/vue-devtools-bug.git

cd vue-devtools-bug

npm install

npm run serve

open chrome devtools

What is expected?

nothing happend

What is actually happening?

memory leak caused by vue-devtools

[raphaelsoul]

leak report by mocha.

I'am using vue-devtools v4.1.5 beta on chrome

[peey]

I've noticed a memory leak in Firefox as well. Browser Version 64.0 (64-bit) on Ubuntu 16.04, Vue Devtools version 4.1.5.

[dpiquet]

Same here, firefox quantum 65, devtools 4.1.5.

I noticed that refreshing the page (ctrl+R) grows memory quite fast when app (spa) built in 'dev' mode. Closing the tab and opening a new one frees the memory.

If the app is in prod mode, devtool plugin is not started and memory usage is normal.

hope that helps to reproduce issue.

[Akryum]

Could you try with the latest 5.0 beta?

[dpiquet]

I still got the issue with 5.0.0 beta 4 installed from github releases.

[lamka02sk]

Still an issue, one big nasty memory leak. I was wondering why my disk makes noise after a few hours of development and found out it was actually swapping. 10GB of RAM only Firefox 😂

[luka-mikec]

I'm not sure if this is related, but a serious leak (~100MB/sec) occurs when I select a component which has a proxied object whose length is (being reported through the proxy as) 10^15. I guess it has to do with JSON stringification somewhere. Perhaps stringifier should not try to stringify everything at once?

[peey]

Status of this bug should be elevated. I have to use Devtools in a secondary browser so that my tabs on primary browser don't crash when I have to kill the process due to memory leak.

[Faymir]

Same for me. huge memory leak when refreshing it goes from 1GB of ram to 3Gb of ram used when refresh just 6 times.

[jcloutz]

Same for me, firefox gets up to around 6GB of ram in less than an hour of working.

[LockonZero]

Same here. I am working with a medium sized set of data and after refreshing a few times, Firefox is using ~5GB of RAM. Closing the tab and starting on a new one temporarily solves the problem