mongoc_cursor_t leaks mongoc_read_concern_t

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 1.3.0-rc0
    • Affects Version/s: 1.3.0-beta0
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ==20354== 144 bytes in 1 blocks are definitely lost in loss record 52 of 116         
      ==20354==    at 0x4C2BBCF: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
      ==20354==    by 0x80F581: _emalloc (zend_alloc.c:2423)                               
      ==20354==    by 0x80F8DF: _safe_emalloc (zend_alloc.c:2539)                          
      ==20354==    by 0x80FA2B: _ecalloc (zend_alloc.c:2566)                               
      ==20354==    by 0x93378D0: php_phongo_calloc (php_phongo.c:2031)                     
      ==20354==    by 0x92DF708: bson_malloc0 (bson-memory.c:103)                          
      ==20354==    by 0x930BE6F: mongoc_read_concern_new (mongoc-read-concern.c:47)        
      ==20354==    by 0x930BE99: mongoc_read_concern_copy (mongoc-read-concern.c:59)          
      ==20354==    by 0x92F9CA0: _mongoc_cursor_new (mongoc-cursor.c:225)                  
      ==20354==    by 0x92EBD8B: mongoc_client_command (mongoc-client.c:1177)              
      ==20354==    by 0x932EC6C: phongo_execute_command (php_phongo.c:621)                 
      ==20354==    by 0x92B4CB7: zim_Manager_executeCommand (Manager.c:134)                
      ==20354==                                                                            
      

              Assignee:
              Hannes Magnusson (Inactive)
              Reporter:
              Hannes Magnusson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: