Remove reachability-based memory sweeps from PerlOnJava
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 5/100
Research direction
Start by inspecting the WIP candidate branch wip/issue2043-preserve-diagnostic-20261113-082631 at commit 386856ab30, not the older PR #1938 head. Trace the failing DBIx phantom-chain regression from its acquisition point through the owner-slot lifetime boundary, using the existing diagnostic trace only to locate the mismatch. The integrator owns shared owner-ledger and lifecycle files; the sweep/walker removal and system-Perl evidence belong in separate worktrees. Done means no graph walk or sweep changes liveness, and focused JVM/interpreter checks plus t/52leaks.t, t/100populate.t, and CPAN acceptance pass.
Written by the indexing model from the issue text.
Description
Goal
Remove reachability-based lifecycle decisions and memory sweeps. Perl strong references must use explicit owner slots with balanced acquisition and release. Historical origin: #1649.
Current checkpoint — 2026-11-19
PR #1938 remains open at remote head 75dd7d542f1f86bff930beb1c5779be74fa27955 on wip/alias-cell-ownership-20261030-185849; the hosted checks reported so far pass and no human review is recorded. The local continuation is on wip/issue2043-preflight-20261119-120058, with HEAD at ddd9e7f0b67762a51fd75f7a5cfca09bdf850688 and uncommitted runtime, regression, and design changes that are not on the PR. The checkout is not ready for UAT.
UAT and CPAN runs still need to clear the Moo accessor-weaken.t optree-reaping failure, Template Toolkit t/string.t counted-scalar replacement failure, and DBIx aggregate cleanup failures. Tracked Java regressions now cover destroyed hash/array outgoing edges, scalar-reference ownership, nested frames, owner-kind count consistency, stale aggregate owner slots, and reusable cleanup-probe state.
The latest unfiltered nice -n 19 timeout 3600 make test-unit passed in 7m43 (/private/tmp/issue2043-cleanup-probe-unit-extended.log); make check-links passed with 0 errors. Excel-Writer-XLSX/t/regression/chart_axis28.t passed 1/1 under the rebuilt candidate. Its diagnostics recorded 1,467 recursive-release roots across 360 worksets and 499 cleanup-target pre-scan roots across 125 reusable worksets. Owner-slot visits remained near 62,000. A four-second JFR allocation sample was noisy and did not establish a total allocation or throughput reduction. The full CPAN release-acceptance gate has not yet run on this candidate.
Allocation minimization plan
Allocation reduction is a completion requirement for sweep removal alongside lower scan cost and correct Perl lifetime behavior. Keep per-frame LIFO cleanup and the explicit owner ledger; use maintained O(1) owner-kind counts for common yes/no checks and retain identity indexes only where identities are needed. Reuse lazy per-frame queues, recursive-release worksets, and cleanup-target probe queues/visited sets across roots instead of allocating a collection per candidate element. The focused chart test's probe workset initializations fell from one per 499 calls to 125 reusable worksets, about 75% fewer for that path. The duplicate direct weak-slot pass was folded into the probe.
The next implementation step is to release the dying aggregate's outgoing owner slots directly, avoiding nested target pre-scans and repeated incoming-owner ledger scans while preserving shared-owner, weak-reference, and destructor-rescue behavior. Track owner-slot visits, pre-scan roots/worksets, queue growth, and append/drain counts separately. Use paired JFR and elapsed-workload measurements on the same CPAN target; the short current recordings are diagnostic evidence only, not a speedup claim. Keep changes only when allocation and scan costs both improve and the hash, array, scalar-reference, and nested-frame regressions pass.
Validation
Earlier merged UAT candidate
nice -n 19 timeout 1800 makepasses on source commit5c011dfa0ein 9m36 (/private/tmp/issue2043-merged-uat-make.log).make check-linkspasses with 855 links checked and 0 errors (/private/tmp/issue2043-merged-uat-check-links-current.log).- The UAT launcher reports
5c011dfa0e; the smoke command printsUAT_OK. dev/modules/dbix_failed_connect_releases_handle.tpasses 3/3 anddev/modules/dbix_failed_connect_releases_storage.tpasses 4/4 on JVM and interpreter; system Perl validation is recorded in the design handoff.- On the merged candidate, DBIx
t/storage/error.tpasses 49/49 with no leaks.t/storage/txn.thas one exception line-reporting mismatch at assertion 89, present before the ownership fix; it reports no leaked references, while system Perl passes 128/128. The interpreter CPAN attempts previously hit their 300-second limits. - The full eight-target
make test-cpan-release-acceptanceremains incomplete. The prior run reached DBIx failures and ended before Excel finished; the isolated Excel profiling run below was deliberately stopped after capturing JFR and is not a module pass. - Current hosted checks for PR head
75dd7d542f1f86bff930beb1c5779be74fa27955pass; the PR is open and has no human review recorded.
Current local candidate
nice -n 19 timeout 3600 make test-unitpasses in 7m43 after the reusable cleanup-target probe change (/private/tmp/issue2043-cleanup-probe-unit-extended.log).- The final documentation link check passes with 0 errors (
/private/tmp/issue2043-check-links-final.log). - Focused
Excel-Writer-XLSX/t/regression/chart_axis28.tpasses 1/1; diagnostics and JFR are recorded at/private/tmp/issue2043-cleanup-probe-chart-axis28-metrics-29217.jsonand/private/tmp/issue2043-cleanup-probe-chart-axis28.jfr. - Full
makeand the eight-targetmake test-cpan-release-acceptanceremain required on the final immutable candidate. Stop at an actionable CPAN failure, preserve its evidence, fix it, and restart the gate on a new candidate.
Remaining work
- Replace nested cleanup-target pre-scans and repeated incoming-owner checks with processing of the exact outgoing owner slots of dying arrays and hashes. Preserve weak observers, live shared aggregates, scalar-reference semantics, and destructor rescue.
- Measure scan visits, workset and queue allocations, sampled allocations, and elapsed time on the same
Excel::Writer::XLSXworkload; require paired evidence before claiming a broad speedup. - Run focused regressions for the previously observed Moo, Template Toolkit, and DBIx failures, then
nice -n 19 makeand the complete eight-target CPAN release-acceptance gate on one immutable source candidate. Stop after an actionable failure, fix it before continuing, and rerun required gates on the resulting candidate. The fork failure remains waived by the user. - Reconcile the tested local candidate with PR #1938, publish only after required gates pass, and wait for human review. Do not mark the checkout UAT ready or merge before final evidence.
After #2043 lands, resume #2037 archive-lifetime and #2034 localized-STDERR work separately.
- Dominant language
- Perl
- Stars
- 67
- Forks
- 8
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 131
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fglock/PerlOnJava
-
area:cpan-port bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fglock/PerlOnJava#2153 ·
Maintainers usually reply within 1 day
-
area:cpan-port area:parser bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fglock/PerlOnJava#2137 ·
Maintainers usually reply within 1 day
-
area:backend area:cpan-port area:runtime bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fglock/PerlOnJava#2071 ·
Maintainers usually reply within 1 day
-
area:runtime documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fglock/PerlOnJava#1579 ·
Maintainers usually reply within 1 day
-
area:cpan-port bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
fglock/PerlOnJava#2157 ·
Maintainers usually reply within 1 day
All issues in fglock/PerlOnJava
Similar issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOpenteam-cli
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
inverse-inc/packetfence#9728 ·
Maintainers usually reply within 1 day
-
fix(char-create): show the real reason a character is refusedPossibly taken @baphomello claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day