libtest-memorygrowth-perl 0.04-4 source package in Ubuntu
Changelog
libtest-memorygrowth-perl (0.04-4) unstable; urgency=medium * Disable Recommends on libdevel-mat-perl temporarily as long as it doesn't build reliably (cf. #1026046). -- gregor herrmann <email address hidden> Tue, 13 Dec 2022 20:02:02 +0100
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Oracular | release | universe | misc | |
Noble | release | universe | misc | |
Mantic | release | universe | misc | |
Lunar | release | universe | misc |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
libtest-memorygrowth-perl_0.04-4.dsc | 2.4 KiB | 3751ecacf13059e8991a6252b7ef26e680b773df4a3e347c26d66cae1cf72605 |
libtest-memorygrowth-perl_0.04.orig.tar.gz | 15.3 KiB | a065852752abd49e4115b98f6db46c752cbbd5e3e48ed0145cee392f793d2ed0 |
libtest-memorygrowth-perl_0.04-4.debian.tar.xz | 2.1 KiB | fba0b879680d558c55192feaacceed7469665e82b41e60e7430e81f6555f09c3 |
Available diffs
- diff from 0.04-3 to 0.04-4 (620 bytes)
No changes file available.
Binary packages built by this source
- libtest-memorygrowth-perl: 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.