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

Posted to issues@lucy.apache.org by "Marvin Humphrey (Updated) (JIRA)" <ji...@apache.org> on 2011/12/12 20:59:31 UTC

[lucy-issues] [jira] [Updated] (LUCY-187) Adapt to GC changes in Perl 5.15

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

Marvin Humphrey updated LUCY-187:
---------------------------------

    Description: 
Perl 5.15 adds a new phase during global destruction which invokes
DESTROY on unreferenced SVs.  This is causing a tripwire exception
when VTable's DESTROY method gets called (VTable_Destroy() should
*never* be called).  However, the fix is more involved than simply
disabling the tripwire.

  was:
Perl 5.15 adds a non-deterministic garbage collection phase during
global destruction where DESTROY is called on any remaining objects
in effectively random order; previously Perl had not invoked DESTROY,
but had merely freed the SVs.  This is causing a tripwire exception
when VTable's DESTROY method gets called (VTable_Destroy() should
*never* be called).  However, the fix is more involved than simply
disabling the tripwire.

        Summary: Adapt to GC changes in Perl 5.15  (was: Adapt to non-deterministic GC in Perl 5.15)
    
> Adapt to GC changes in Perl 5.15
> --------------------------------
>
>                 Key: LUCY-187
>                 URL: https://issues.apache.org/jira/browse/LUCY-187
>             Project: Lucy
>          Issue Type: Bug
>          Components: Perl bindings
>    Affects Versions: 0.1.0 (incubating), 0.2.0 (incubating), 0.2.1 (incubating), 0.2.2 (incubating)
>            Reporter: Marvin Humphrey
>            Assignee: Marvin Humphrey
>             Fix For: 0.3.0 (incubating)
>
>         Attachments: 0001-LUCY-187-Bind-to-correct-destructors.patch, 0002-LUCY-187-Disable-DESTROY-during-global-destruction.patch
>
>
> Perl 5.15 adds a new phase during global destruction which invokes
> DESTROY on unreferenced SVs.  This is causing a tripwire exception
> when VTable's DESTROY method gets called (VTable_Destroy() should
> *never* be called).  However, the fix is more involved than simply
> disabling the tripwire.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira