-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 option #41
Comments
Memory leaks really depend on the browser/environment so I don't think that JSHint could be of any help here. Unless you know of any generic, easy-to-catch example? |
Sadly, I don't. Hope someone else can provide an example |
JSHint cannot possibly know if you're intending to use certain information in the future or not (information which you save/reference, but that you don't want to use in the future is what I'd consider a memory leak). Normally memory leaks are considered to be the problem of browser implementors - i.e. bad garbage collection, if I'm not mistaken. |
Closes jshint#41 (hopefully)
like the title says, I would love to see a Memory Leak detection option to help optimize any/all JS code
The text was updated successfully, but these errors were encountered: