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 option #41

Closed
gregmax17 opened this issue Feb 20, 2011 · 3 comments
Closed

Memory Leak option #41

gregmax17 opened this issue Feb 20, 2011 · 3 comments

Comments

@gregmax17
Copy link

like the title says, I would love to see a Memory Leak detection option to help optimize any/all JS code

@valueof
Copy link
Member

valueof commented Apr 10, 2011

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?

@valueof valueof closed this as completed Apr 10, 2011
@gregmax17
Copy link
Author

Sadly, I don't. Hope someone else can provide an example

@Skalman
Copy link

Skalman commented Apr 11, 2011

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.

danielctull pushed a commit to danielctull-forks/jshint that referenced this issue Jan 14, 2018
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

3 participants