Funny u mention the two lines. I left everything commented out *except*
the first CIDR SNMP call, did nothing with the results, just let the
data go nowhere, and the memory leak returned. Instead of using
in the 700 meg range otherwise, it's now 1.2 GB. With that one call
alone.
Net::SNMP is pure Perl so should theoretically be thread safe.
None of the objects are instantiated until we're working on a
specific device. I call destroy on it at the end of its usage
and even if it were left alone it should be overwritten at each
loop.
sub wreckobject {
$session->close;
undef $session;
}
And if my SNMP usage is fundamentally flawed u'ld think that all
the other calls would blow it up far worse than the routing
table lookups. I'll play around with various usages of the object,
see if anything changes. The Net::SNMP module was the one thing
even in the beginning I was hoping there was nothing wrong with and
I did have a Murphy's Law gut feeling that the problem was in there.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.