That just means that the module does get_next_request's to walk the logical column of the snmp table. Once the walk result is no longer a child of the argument, it stops and returns. I dumped $result6 and it's contents were exactly what I expected. I dumped it pre and post execution and it starts off undef and then gets just the routing table data I want. So no surprises there.

I also dumped $session pre and post build and pre and post destruction. No surprises there either. It only retains data from the last snmp call and after the close method is called it doesn't contain any snmp data, just the object definition. I think I know why the routing info blows up the script though. These routing tables can get up to 620 K and if some leaked variable is hanging onto them then that will add up fast. That would also mean that all the calls are leaking, just that they contain less data.