|
|
|
| We don't bite newbies here... much | |
| PerlMonks |
Re^3: Debugging DESTROY calls in forking applicationby cavac (Parson) |
| on Mar 11, 2020 at 11:21 UTC ( [id://11114120]=note: print w/replies, xml ) | Need Help?? |
|
Yeah, memory leaks is one of the worst class of bugs. If they happen more if the system is busier, this is even worse. If, for example, your webserver code leaks memory with every page visited, everything is fine while you don't have much visitors. The first time a news article links to your site everything will halt and catch fire...
perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||