-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
"MaxListenersExceededWarning: Possible EventEmitter memory leak detected" when creating models with autoCreate: true
before mongoose.connect()
#9778
Labels
confirmed-bug
We've confirmed this is a bug in Mongoose and will fix it.
Milestone
Comments
vkarpov15
added
the
needs repro script
Maybe a bug, but no repro script. The issue reporter should create a script that demos the issue
label
Jan 8, 2021
It also happens when I use |
Will someone look at this? |
|
IslandRhythms
added
can't reproduce
Mongoose devs have been unable to reproduce this issue. Close after 14 days of inactivity.
and removed
needs repro script
Maybe a bug, but no repro script. The issue reporter should create a script that demos the issue
labels
Feb 22, 2021
@IslandRhythms @vkarpov15 just add |
|
IslandRhythms
added
confirmed-bug
We've confirmed this is a bug in Mongoose and will fix it.
has repro script
There is a repro script, the Mongoose devs need to confirm that it reproduces the issue
and removed
can't reproduce
Mongoose devs have been unable to reproduce this issue. Close after 14 days of inactivity.
confirmed-bug
We've confirmed this is a bug in Mongoose and will fix it.
labels
Feb 23, 2021
This problem does not exist on the most recent version of mongoose. |
vkarpov15
added
can't reproduce
Mongoose devs have been unable to reproduce this issue. Close after 14 days of inactivity.
and removed
has repro script
There is a repro script, the Mongoose devs need to confirm that it reproduces the issue
labels
Mar 1, 2021
IslandRhythms
added
confirmed-bug
We've confirmed this is a bug in Mongoose and will fix it.
can't reproduce
Mongoose devs have been unable to reproduce this issue. Close after 14 days of inactivity.
and removed
can't reproduce
Mongoose devs have been unable to reproduce this issue. Close after 14 days of inactivity.
confirmed-bug
We've confirmed this is a bug in Mongoose and will fix it.
labels
Mar 23, 2021
IslandRhythms
removed
the
can't reproduce
Mongoose devs have been unable to reproduce this issue. Close after 14 days of inactivity.
label
Mar 23, 2021
@vkarpov15 its very finicky but I can reproduce it but I'm not sure what triggers it. |
IslandRhythms
added
the
confirmed-bug
We've confirmed this is a bug in Mongoose and will fix it.
label
Mar 23, 2021
vkarpov15
changed the title
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 open listeners added to [NativeConnection]. Use emitter.setMaxListeners() to increase limit
"MaxListenersExceededWarning: Possible EventEmitter memory leak detected" when creating models with Mar 31, 2021
autoCreate: true
before mongoose.connect()
vkarpov15
added a commit
that referenced
this issue
Apr 11, 2021
…when using `setClient()` Re: #9778
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Bug report
What is the current behavior?
When creating more than 10 models
MaxListenersExceededWarning
appearsIf the current behavior is a bug, please provide the steps to reproduce.
Create more than 10 models like this:
If you are using TypeScript, please include your
tsconfig.json
What is the expected behavior?
Should create more models without warnings
What are the versions of Node.js, Mongoose and MongoDB you are using? Note that "latest" is not a version.
Currently I solved the issue by calling the following function each time before creating models:
but I think there should be another solution for this.
The text was updated successfully, but these errors were encountered: