in reply to
Hunting a memory eater
Why do you create a separate resolver object for each query?
I don't do it this way in my code. But a cpan module, I'm using is using Net::DNS in more or less this way. While searching for the culprit I could reduce it to the snippet shown by me.
So, you're absolutly right that someone should instantiate one resolver object and then use this resolver for 1..n lookups.
In terms of memory usage I would expect that all memory gets freed when the reference to the object gets out of scope.
The moon would crash into the Earth
The moon would breakup at the Roche limit
The wire would turn the Earth into a giant electromagnet
The Earth would turn into a giant yo-yo.
The moon would orbit every ~24 hours, significantly changing the lunar calendar
The centripetal force would rip out the Earth's core
All man-made satellites would be destroyed, causing great havoc
Moon landings would become significantly easier
The rope or wire would break, no matter how strong it was
The Vulcans would show up for First Contact causing yet another revision to the timeline
The Galactic Police would snip the rope and put the Earth on probation
Some idiot would get terrible, terrible, rope burn
We finally get those golf balls back
Results (717 votes),