-
Notifications
You must be signed in to change notification settings - Fork 27
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
warning: possible EventEmitter memory leak detected #64
Comments
+1 |
Yeah, this is for real. Every time the plugin is called the
Just add: |
@benoitguigal to fix this do this to your
And please give me that bounty on SO 😃 |
This seems like a real bug, looking into it. |
So my SO solution doesn't work right. Luckily I have another solution in the interim until a PR is made. So try this: Edit From Your original code should work. |
Thanks Freyert, I will give it a try :-) |
Cheeeers, has fixed for me |
BTW @benoitguigal and @neilcarpenter nice sites/projects. |
Haha thanks!! :) And yeah, ditto to @benoitguigal |
+1, is there still no PR or merged code for this? |
+1 |
this seems to be an issue still with browserify ./client/src/app/*.js -p [ factor-bundle -o 'uglifyjs -cm > ./client/dist/js/`basename $FILE`' ] -o ./client/dist/js/common.js the above "fix" does not solve the issue... |
This was still a problem I had in my grunt karma task
I got it to stop by trying this line for an arbitrary number
I continued to get warnings that I had So if you're willing to sit down and find out how many listeners you've been adding, you can at least silence the warning by using the line above somewhere in the global scope. |
I defined my browserify + watchify task exacly as here and got this problem as well.
|
Why this has not been fixed yet? |
I used this ugly workaround, since I was not able to extract the plugin outside rebundle function
|
I am using factor-bundle with watchify and gulp.
It works fine but after five or ten rebundles I start seeing the following warning:
The text was updated successfully, but these errors were encountered: