You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucy.apache.org by "Nick Wellnhofer (JIRA)" <ji...@apache.org> on 2017/02/23 16:28:44 UTC

[lucy-issues] [jira] [Resolved] (CLOWNFISH-117) Potential memory corruption during Perl global destruction

     [ https://issues.apache.org/jira/browse/CLOWNFISH-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Wellnhofer resolved CLOWNFISH-117.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.7.0

Fixed with https://git1-us-west.apache.org/repos/asf?p=lucy-clownfish.git;a=commitdiff;h=4aea9977c3d25a550cd72d95a4e2493da3711a3a

> Potential memory corruption during Perl global destruction
> ----------------------------------------------------------
>
>                 Key: CLOWNFISH-117
>                 URL: https://issues.apache.org/jira/browse/CLOWNFISH-117
>             Project: Apache Lucy-Clownfish
>          Issue Type: Bug
>          Components: Perl, Runtime
>            Reporter: Nick Wellnhofer
>             Fix For: 0.7.0
>
>
> During global destruction, DESTROY is called in random order on objects remaining because of refcount leaks or circular references. This can cause memory corruption with Clownfish objects. Since many exceptions leak refcounts, this can happen if a Perl process exits after an exception was thrown.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)