in reply to Re^6: Massive Perl Memory Leak
in thread Massive Perl Memory Leak
I can just imagine a situation where threads don't know who's supposed to be doing what with the process heap.
Barring bugs where something scribbles on memory it shouldn't, I have a difficult time believing that threads will suddenly forget they own SVs. It's not as if you have to sweep memory pools with a refcounting system.
If data is in a state where it "should" be garbage collected, then there's nothing to check a ref count of.
Ref counting is how Perl decides to collect data! How do you separate the two things when the former depends on the latter?
When variables die Perl only guarantees that the varname is no longer accessible....
I don't know what it means for a variable to "die". Regardless, if what you said were true--if there were some connection to variable name and liveness--then I don't see how anonymous variables would work.
... not that anything in particular has been done with the SV's behind the scenes.
The ref count is part of the SV structure!
|
|---|