Debian Codegraph @

debian/control

raw
1 Source: libtest-memorygrowth-perl
2 Maintainer: Debian Perl Group <[email protected]>
3 Uploaders: gregor herrmann <[email protected]>
4 Section: perl
5 Testsuite: autopkgtest-pkg-perl
6 Priority: optional
7 Build-Depends: debhelper-compat (= 13),
8 libmodule-build-perl,
9 libtest2-suite-perl <!nocheck>,
10 perl
11 Standards-Version: 4.7.0
12 Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libtest-memorygrowth-perl
13 Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libtest-memorygrowth-perl.git
14 Homepage: https://metacpan.org/release/Test-MemoryGrowth
15 Rules-Requires-Root: no
16
17 Package: libtest-memorygrowth-perl
18 Architecture: all
19 Multi-Arch: foreign
20 Depends: ${misc:Depends},
21 ${perl:Depends}
22 # libdevel-mat-perl has build issues, cf. #1026046
23 # libdevel-mat-perl
24 Recommends: libdevel-mat-dumper-perl
25 Description: module to assert that code does not cause growth in memory usage
26 Test::MemoryGrowth provides a function to check that a given block of code
27 does not result in the process consuming extra memory once it has finished.
28 Despite the name of this module it does not, in the strictest sense of the
29 word, test for a memory leak: that term is specifically applied to cases
30 where memory has been allocated but all record of it has been lost, so it
31 cannot possibly be reclaimed. While the method employed by this module can
32 detect such bugs, it can also detect cases where memory is still referenced
33 and reachable, but the usage has grown more than would be expected or
34 necessary.
35 .
36 The block of code will be run a large number of times (by default 10,000),
37 and the difference in memory usage by the process before and after is
38 compared. If the memory usage has now increased by more than one byte per
39 call, then the test fails.