Possible memory leak created by watchers

Vue version

a95554d

Link to minimal reproduction

https://sfc.vuejs.org/#eNqFkcFugzAMhl/FyqUgUbJdK1pp2mVPsFMuAdxBFZLICXBAvPsMlGnapPaEf/vzj/xnEm/e50OP4iSKUFHrIwSMvb8o23beUYQJCHUV2wEzGHWsGpjhSq6DA68dlFW2MjoE+HxfP5OyAAOc4UXZeal57myIoLm3OyUWx/tCkqY7UT4glF3/negMkhTOF5jmlAspod8mUGljsN65DSqf0oXcruZ7WUTsvNERWQEUzevlA41xMDoydSFZLws/kMjEltGx0z6/BWc5xfV+dR8EJU5bIkuP81q0Ek2MPpykDNdqyf4WckdfkqucehvbDnMM3bEkNwYkNlYi++UhuTkgHQltjYT0yPMP+s93seVXmsX8DUUcsN0=

Steps to reproduce

1. Start chrome
2. Open the linked SFC Playground
3. Open devtools > Memory
4. Invoke garbage collection (click on trash)
5. Create snapshot
6. In the created snapshot, filter for VClass objects

What is expected?

If I'm not mistaken, both a and b should be garbage collected.

What is actually happening?

Only a is being garbage collected.

System Info

No response

Any additional comments?

No response

[miroljub1995]

If you open JS tab in a playground you will see that a and b are returned from setup and available to use in render from $setup argument, so they should not be collected after setup.

[edison1105]

Only a is being garbage collected.

I can't reproduce this. Both a and b are found in snapshots.

like @miroljub1995 said, they should not be collected.