Avoid repeated reachability walks while Moose modules initialize
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
Direzione di ricerca
Start in WeakRefRegistry.weaken(), at the weakenedLiveBlessedRef condition, where reachableOwnerCount() is evaluated before ModuleInitGuard.inModuleInit(). Follow reachableOwnerCount() into ReachabilityWalker.isScalarReachable() to see the root walk. Reorder the check, add a deterministic regression test for module initialization, and confirm weak-reference behaviour outside module init. Done when t/05_round.t finishes on both the JVM and interpreter backends.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Loading StorageDisplay 1.0.11 through Moose triggers a large number of Scalar::Util::weaken calls. For live blessed references, WeakRefRegistry.weaken() calls reachableOwnerCount(), which repeatedly walks the Perl object graph. The module-initialization guard is checked only after this expensive query, so it does not suppress the work during module loading. The repeated walks make t/05_round.t exceed the CPAN tester timeout on both PerlOnJava backends.
Evidence
- CPAN random tester run:
20261102-094403-98885 - Distribution:
StorageDisplay-1.0.11; failing test:t/05_round.t - System Perl 5.42.2: full suite passed, 7 files / 85 tests, in about 6 seconds.
- PerlOnJava 5.44.1 / Java 24.0.2: CPAN run timed out after 120 seconds with no output for 60 seconds. Focused runs of
t/05_round.twith the archived dependency overlay exceeded a 40-second hard timeout on both JVM and interpreter backends. - An 8-second JVM Flight Recorder profile of
use StorageDisplayshowed repeated stacks throughScalarUtil.weaken,RuntimeBase.reachableOwnerCount, andReachabilityWalkerroot traversal. This is repeated work, not evidence of an infinite loop.
StorageDisplay is pure Perl and uses Moose 2.4000 and namespace::sweep 0.006. The PerlOnJava report showed t/000-report-versions.t passing before the harness stopped producing output.
Suspected cause
In WeakRefRegistry.weaken(), the condition at the weakenedLiveBlessedRef check evaluates base.reachableOwnerCount() == 0 before !ModuleInitGuard.inModuleInit(). reachableOwnerCount() checks each active owner using ReachabilityWalker.isScalarReachable(), which traverses the global root graph. Moose performs many such weaken operations while required modules execute under ModuleInitGuard, multiplying full root walks during initialization.
Move the module-init check ahead of the reachability query, then confirm the same behavior is preserved outside module initialization.
Acceptance criteria
- Add deterministic regression coverage proving module initialization does not perform the expensive reachable-owner walk for this path.
- Run new/changed Perl-level coverage with system Perl first.
t/05_round.tcompletes under PerlOnJava's JVM and interpreter backends with the archived dependency load order.- Run the required build and lifecycle tests; retain bounded output and verify weak-reference semantics outside module initialization.
Related: #1642 and merged PR #1746 addressed other repeated reachability paths during cleanup. This CPAN case reproduces through WeakRefRegistry.weaken() during module initialization.
- Lingua principale
- Perl
- Stelle
- 65
- Fork
- 8
- Merge medio
- 5h 49m
- PR unite (30g)
- 177
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di fglock/PerlOnJava
-
area:runtime documentation enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
fglock/PerlOnJava#1579 ·
I maintainer di solito rispondono entro 1 giorno
-
Autovivify undefined hash reference in list assignmentForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertaarea:runtime bug
Difficoltà 4/5 1-2 giorni Idoneità per principianti 55/100
fglock/PerlOnJava#1958 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
area:io bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 56/100
fglock/PerlOnJava#1957 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
fglock/PerlOnJava#1955 ·
I maintainer di solito rispondono entro 1 giorno
-
area:runtime bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 22/100
fglock/PerlOnJava#1951 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di fglock/PerlOnJava
Issue simili
-
wave-followup
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
-
benchmarks/README: 'perl BNG2.pl model.bngl' runs the whole protocol, not just generate_networkApertadocumentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
virtualmin/virtualmin-gpl#1322 ·
-
`singletitle`/`uniquetitle`/`uniquework` only ignore entries whose `options` field contains the literal token `skipbib`; `skipbib=true` and `dataonly` still countForse già presa @plk l’ha presa 1 giorno fa. ApertaBug fixedindev
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
easy first-contributor first-contributors good first issue help wanted perl shell up-for-grabs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
fork-commit-merge/fork-commit-merge#8461 ·
I maintainer di solito rispondono entro 1 giorno