-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.0, 3.0.1, 3.0.2, 3.0.3, 3.1, 3.1.1, 3.2, 3.2.1, 3.2.2, 3.3, 3.3.1, 3.4, 3.5, 3.6
-
Component/s: Internal
-
None
-
Environment:Linux
OSX
Cursors which get garbaged collected get put into the backlog queue of the mongo_client to be cleaned up in a background thread.
However, if the mongo_client is GC'ed before the background thread has had a chance to run, the cursor will not be closed correctly. This becomes a major problem when the {{ no_cursor_timeout }} option is enabled.