You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mongodb(the binary version): not relevant, quickest to notice is 7.0.14
mongodb(the js package): not relevant
system: linux, but likely others
package: mongo-memory-server-core
What is the Problem?
It seems like when we do child_process.fork now, it implies --import PRELOAD if the original process has been started with --import, like in the following example.
This causes the PRELOAD to be re-executed upon forking to the killer_script, causing a infinite loop of starting and never cleaning-up extra mongo servers.
Versions
package: mongo-memory-server-core
What is the Problem?
It seems like when we do
child_process.fork
now, it implies--import PRELOAD
if the original process has been started with--import
, like in the following example.This causes the
PRELOAD
to be re-executed upon forking to thekiller_script
, causing a infinite loop of starting and never cleaning-up extra mongo servers.see #907 (comment)
Code Example
Execute with:
Debug Output
no output by default as we disable stdio for the forked process
Do you know why it happenes?
Yes, as described above.
The text was updated successfully, but these errors were encountered: