[ https://issues.apache.org/jira/browse/AVRO-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16715365#comment-16715365 ]
ASF subversion and git services commented on AVRO-766: ------------------------------------------------------ Commit b597c3ab93ef1c6a37a9c1fa3584d86d20723784 in avro's branch refs/heads/master from John Gill [ https://gitbox.apache.org/repos/asf?p=avro.git;h=b597c3a ] AVRO-1167, AVRO-766: Fix c AVRO_LINK memory leaks (#217) * AVRO-1167: Enhance avro_schema_copy for AVRO_LINK - Add hash of named schemas found during copy - Find saved named schema for copy of AVRO_LINK * AVRO-766: Correct memory leaks in AVRO_LINK copy - Adds test cases for AVRO-766 & AVRO-1167 - Corrects reference counting for avro_schema_copy * Enable TEST_AVRO_1167 in test_avro_766 This ensures that both fixes work together and that no valgrind errors are produced from a recrusive schema. > C: Memory leak from reference count cycles > ------------------------------------------ > > Key: AVRO-766 > URL: https://issues.apache.org/jira/browse/AVRO-766 > Project: Apache Avro > Issue Type: Bug > Components: c > Affects Versions: 1.5.0 > Reporter: Douglas Creager > Priority: Major > Attachments: AVRO-766.patch, ref-cycle.c > > > If you parse a recursive Avro schema, you end up with a cycle in the > reference graph for the avro_schema_t objects that are created. The > reference counting mechanism that we're using can't detect this, and so you > get a memory leak. -- This message was sent by Atlassian JIRA (v7.6.3#76005)