Re^5: Tracing memory leak

No, it does not

Ah, you're right. XS does an implicit sv_2mortal() of the returned RV, which is why it doesn't get leaked. I guess Inline::C must do something similar (I've never used Inline::C). The problem I perceived however wouldn't have been circumvented by the _noinc usage.

Dave.

Comment on Re^5: Tracing memory leak Download Code

Replies are listed 'Best First'.
Re^6: Tracing memory leak by halfcountplus (Hermit) on Sep 14, 2011 at 23:04 UTC
The problem I perceived however wouldn't have been circumvented by the _noinc usage. Heh-heh -- I was going to add something like "or else you have assumed something more chimeric about the RV" since based on the empirical it seemed to me this is just a pointer value but your explication explicates (namely the implicit sv_2mortal, and the implication that the RV is a scalar tracked by perl, not just a pointer value), cool. I am very new to perl internals. PL_sv_count does indicate an issue but I am too beat for this evening. Thanks!	[reply]

Replies are listed 'Best First'.

Re^6: Tracing memory leak
by halfcountplus (Hermit) on Sep 14, 2011 at 23:04 UTC

The problem I perceived however wouldn't have been circumvented by the _noinc usage.

Heh-heh -- I was going to add something like "or else you have assumed something more chimeric about the RV" since based on the empirical it seemed to me this is just a pointer value but your explication explicates (namely the implicit sv_2mortal, and the implication that the RV is a scalar tracked by perl, not just a pointer value), cool. I am very new to perl internals.

PL_sv_count does indicate an issue but I am too beat for this evening. Thanks!

[reply]