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
Javascript error, memory leak and other assorted explosions #987
Comments
Probably important to mention that you see this error in your developer tools console... |
Sorry, yes, all of the above errors are seen in the Chrome developer tools console. |
It's happening on firefox too. |
To fix the EventEmitter bug we just need to upgrade to the latest browserify. I'm working on that. |
valueof
added a commit
that referenced
this issue
Apr 8, 2013
This is fixed on master. |
jugglinmike
pushed a commit
to jugglinmike/jshint
that referenced
this issue
Oct 21, 2014
This should improve performance on Rhino and resolve EventEmitter leaks. Closes jshintGH-983. Closes jshintGH-958. Closes jshintGH-931. Closes jshintGH-889. Affects jshintGH-987.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I enter the following snippet of code at JSHint.org (yes, I know there is a missing
)
in theif
statement line, that's part of the problem):I see the following error:
If I continue to click the Lint button, I see these errors:
Then as I continue to click, the initial error repeats... and all this while nothing visible happens on the main page.
Oddly, if I remove the second
.bind()
function, JSHint begins to work as expected.The text was updated successfully, but these errors were encountered: