Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory Leak Problem #79

Closed
songyk674 opened this issue Oct 18, 2018 · 9 comments
Closed

Memory Leak Problem #79

songyk674 opened this issue Oct 18, 2018 · 9 comments

Comments

@songyk674
Copy link

when i use vuescroll in Vue, there hava a memory leak problem, when I leave the page which use vuescroll,the listener action was not release, the component have no release api to destory ,how can i slove this problem? thanks

@wangyi7099
Copy link
Member

hi, what kind of file did you import? vuescroll.js , vuescroll-native.js or vuescroll-slide.js ?

@songyk674
Copy link
Author

i import vuescroll-native.js by npm in main.js。

@wangyi7099
Copy link
Member

Thanks for your feedback. Could you please provide a minimal reproduction?

@songyk674
Copy link
Author

image
when i use chrome to detect the memory leak problem, i find many dom was not releasede ,you can see the screenshot.

@wangyi7099
Copy link
Member

Hi, just had a look at screenshot, didn't find memory leak about vuescroll, could you please provide a repro ? Thanks !

@songyk674
Copy link
Author

vuescroll-example.zip
the attachement is the example of leak memory, you can use chrom browser to check the problem, the artical below is the introduction of chrome how to detect the problem.thanks https://forum.vuejs.org/t/vue/28397

@songyk674
Copy link
Author

do you have any new processd?

@wangyi7099
Copy link
Member

Sorry . I'm bussy moving house these days. And I don't have a desk now, I have to buy one on Taobao.com. And desk is not arriving. I will fix it in the future days. Thanks for your contribution!

@wangyi7099
Copy link
Member

Hi, The reason for this is because window.resize is not released in time. This has been fixed in 4.9.0-beta.1. Try latest version can solve this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants