[
https://issues.apache.org/jira/browse/AVRO-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758507#action_12758507
]
Scott Banachowski commented on AVRO-117:
----------------------------------------
After looking at the flex source, and compiling and testing with versions
2.5.4, 2.5.27, 2.5.31, 2.5.33, 2.5.34 and 2.5.35, I have way more knowledge of
flex than I wanted to know.
The leak this original patch addressed was fixed at 2.5.27, but then at 2.5.31
there was another leak introduced, which was then fixed in 2.5.34.
I now have a compiler switch that can fix both known leaks, and compiles with
all the versions above. I just hope that covers the multiple of flex users.
> plug mem leak from flex parser for C++
> --------------------------------------
>
> Key: AVRO-117
> URL: https://issues.apache.org/jira/browse/AVRO-117
> Project: Avro
> Issue Type: Bug
> Components: c++
> Reporter: Scott Banachowski
> Assignee: Scott Banachowski
> Attachments: AVRO-117.patch
>
>
> Valgrind reports a leak coming from the flex parser generated code.
> The flex-generated lexer allocates memory to use for its state stack.
> Examining this code it is clear that once allocated, the stack is never
> freed. Since I cannot easily replace flex code, I inserted the code to free
> the stack as a lexer rule.
> Valgrind is happy with the result.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
