[jira] [Commented] (ZOOKEEPER-1536) c client : memory leak in winport.c
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445837#comment-13445837 ] Hudson commented on ZOOKEEPER-1536: --- Integrated in ZooKeeper-trunk #1665 (See [https://builds.apache.org/job/ZooKeeper-trunk/1665/]) ZOOKEEPER-1536 c client : memory leak in winport.c (brooklin via michim) (Revision 1379046) Result = SUCCESS michim : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1379046 Files : * /zookeeper/trunk/CHANGES.txt * /zookeeper/trunk/src/c/src/winport.c > c client : memory leak in winport.c > --- > > Key: ZOOKEEPER-1536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1536 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.4.3 > Environment: windows7 >Reporter: brooklin >Assignee: brooklin > Fix For: 3.4.4, 3.5.0 > > Attachments: winport.c.patch > > > At line 99 in winport.c, use windows API "InitializeCriticalSection" but > never call "DeleteCriticalSection" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1536) c client : memory leak in winport.c
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445220#comment-13445220 ] Michi Mutsuzaki commented on ZOOKEEPER-1536: I'm committing this to 3.4 branch right now. --Michi > c client : memory leak in winport.c > --- > > Key: ZOOKEEPER-1536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1536 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.4.3 > Environment: windows7 >Reporter: brooklin >Assignee: brooklin > Fix For: 3.4.4 > > Attachments: winport.c.patch > > > At line 99 in winport.c, use windows API "InitializeCriticalSection" but > never call "DeleteCriticalSection" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1536) c client : memory leak in winport.c
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445172#comment-13445172 ] Mahadev konar commented on ZOOKEEPER-1536: -- Michi is this committed to 3.4 branch as well? > c client : memory leak in winport.c > --- > > Key: ZOOKEEPER-1536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1536 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.4.3 > Environment: windows7 >Reporter: brooklin >Assignee: brooklin > Fix For: 3.4.4 > > Attachments: winport.c.patch > > > At line 99 in winport.c, use windows API "InitializeCriticalSection" but > never call "DeleteCriticalSection" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1536) c client : memory leak in winport.c
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445163#comment-13445163 ] Michi Mutsuzaki commented on ZOOKEEPER-1536: +1. Thank you for the patch, brooklin! --Michi > c client : memory leak in winport.c > --- > > Key: ZOOKEEPER-1536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1536 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.4.3 > Environment: windows7 >Reporter: brooklin >Assignee: brooklin > Fix For: 3.4.4 > > Attachments: winport.c.patch > > > At line 99 in winport.c, use windows API "InitializeCriticalSection" but > never call "DeleteCriticalSection" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
