File: control

package info (click to toggle)
libtest-memorygrowth-perl 0.04-4
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 116 kB
  • sloc: perl: 134; makefile: 2
file content (38 lines) | stat: -rw-r--r-- 1,786 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
Source: libtest-memorygrowth-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: gregor herrmann <gregoa@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper-compat (= 13),
               libmodule-build-perl,
               perl
Standards-Version: 4.6.1
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libtest-memorygrowth-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libtest-memorygrowth-perl.git
Homepage: https://metacpan.org/release/Test-MemoryGrowth
Rules-Requires-Root: no

Package: libtest-memorygrowth-perl
Architecture: all
Multi-Arch: foreign
Depends: ${misc:Depends},
         ${perl:Depends}
# libdevel-mat-perl has build issues, cf. #1026046
# libdevel-mat-perl
Recommends: libdevel-mat-dumper-perl
Description: module to assert that code does not cause growth in memory usage
 Test::MemoryGrowth provides a function to check that a given block of code
 does not result in the process consuming extra memory once it has finished.
 Despite the name of this module it does not, in the strictest sense of the
 word, test for a memory leak: that term is specifically applied to cases
 where memory has been allocated but all record of it has been lost, so it
 cannot possibly be reclaimed. While the method employed by this module can
 detect such bugs, it can also detect cases where memory is still referenced
 and reachable, but the usage has grown more than would be expected or
 necessary.
 .
 The block of code will be run a large number of times (by default 10,000),
 and the difference in memory usage by the process before and after is
 compared. If the memory usage has now increased by more than one byte per
 call, then the test fails.