Upstream software project

libdevel-cycle-perl

find memory cycles in objects

About libdevel-cycle-perl

find memory cycles in objects

This project links 11 native package records across 8 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Alpine Linux 3.21: 2 package records; Alpine Linux 3.22: 2 package records; Alpine Linux 3.23: 2 package records; Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.libdevel-cycle-perl: recorded package coverageAlpine Linux 3.212 recordsAlpine Linux 3.222 recordsAlpine Linux 3.232 recordsDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libdevel-cycle-perl
Publisher
Not authoritatively mapped
Native package records
11
Operating systems
alpine-linux-3-21, alpine-linux-3-22, alpine-linux-3-23, debian-12, debian-13, fedora-43, fedora-44, opensuse-tumbleweed
License expression
GPL-1.0-or-later OR Artistic-1.0-Perl
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This is a simple developer's tool for finding circular references in objects and other types of references. Because of Perl's reference-count based memory management, circular references will cause memory leaks.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Alpine Linux 3.21

  1. Package perl-devel-cycle

    v3.21 (Alpine Linux 3.21): find memory cycles in objects

    1.12-r2: aarch64 x86_64

    Source: perl-devel-cycle

  2. Package perl-devel-cycle-doc

    v3.21 (Alpine Linux 3.21): find memory cycles in objects (documentation)

    1.12-r2: aarch64 x86_64

    Source: perl-devel-cycle

Alpine Linux 3.22

  1. Package perl-devel-cycle

    v3.22 (Alpine Linux 3.22): find memory cycles in objects

    1.12-r2: aarch64 x86_64

    Source: perl-devel-cycle

  2. Package perl-devel-cycle-doc

    v3.22 (Alpine Linux 3.22): find memory cycles in objects (documentation)

    1.12-r2: aarch64 x86_64

    Source: perl-devel-cycle

Alpine Linux 3.23

  1. Package perl-devel-cycle

    v3.23 (Alpine Linux 3.23): find memory cycles in objects

    1.12-r2: aarch64 x86_64

    Source: perl-devel-cycle

  2. Package perl-devel-cycle-doc

    v3.23 (Alpine Linux 3.23): find memory cycles in objects (documentation)

    1.12-r2: aarch64 x86_64

    Source: perl-devel-cycle

Debian 12 (Bookworm)

  1. Package libdevel-cycle-perl

    bookworm (Debian 12 (Bookworm)) (perl): Perl module to detect memory cycles in Perl objects

    1.12-2: all

Debian 13 (Trixie)

  1. Package libdevel-cycle-perl

    trixie (Debian 13 (Trixie)) (perl): Perl module to detect memory cycles in Perl objects

    1.12-2: all

Fedora 43

  1. Package perl-Devel-Cycle

    43 (Fedora 43) (Unspecified): Find memory cycles in objects

    1.12-32.fc43: noarch

    Source: perl-Devel-Cycle

Fedora 44

  1. Package perl-Devel-Cycle

    44 (Fedora 44) (Unspecified): Find memory cycles in objects

    1.12-33.fc44: noarch

    Source: perl-Devel-Cycle

openSUSE Tumbleweed

  1. Package perl-Devel-Cycle

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Find memory cycles in objects

    1.120.0-1.5: noarch

    Source: perl-Devel-Cycle

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.