[CDRIVER-395] Need clarification on mongo c-driver Created: 15/Jul/14 Updated: 03/May/17 Resolved: 16/Jul/14 |
|
| Status: | Closed |
| Project: | C Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Arati Sethy | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux Location: http://www.mongodb.org/about/support/ |
||
| Description |
|
Hi, ------------------------------------------------------------------------------------------------ code snippet. } // end of while(mongo_cursor_next bson_destroy( &b ); |
| Comments |
| Comment by Christian Hergert [ 16/Jul/14 ] |
|
Sorry for the short non-answers above, just cleaning up things before release. Short answer is, it probably does leak in this situation. The legacy driver didn't really have support for tailable cursors, so it is completely untested. I strongly suggest updating your code to use the new driver. It will be faster, safer, and is to the best of our knowledge, leak free. |
| Comment by Christian Hergert [ 16/Jul/14 ] |
|
Marking wont fix as the legacy driver is no longer supported. |
| Comment by Christian Hergert [ 16/Jul/14 ] |
|
Hi, this code is using the legacy driver which is no longer supported. The current version of a C driver has a new API, but also has rigorous valgrind testing. |