X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pages%2Fblog-0022.html-inc;h=c3b4a7626a19050de251e925f4b6eb5ede77c0e0;hb=a05e5d4499fb58198e463162d0385e8a156e1f03;hp=07f93572e8222cb208caab774a8da5e5cca131dd;hpb=769d193e7a4b5eeebd1f248a084ae4f2495df071;p=sdlgit%2FSDL-Site.git diff --git a/pages/blog-0022.html-inc b/pages/blog-0022.html-inc index 07f9357..c3b4a76 100644 --- a/pages/blog-0022.html-inc +++ b/pages/blog-0022.html-inc @@ -1,6 +1,22 @@

-Catching memory leaks in XS +Developer Release of SDL 2.3_1

-
 I slay dragons, yonder

So I am trying to find and plug memory leaks in SDL perl. Most of the memory leaks occur because in XS a reference is still held. One very expensive mem leak was caught by TELS really early on here. The problem occurs where in XS there is

RETVAL = (cast *) safemalloc( ... );
 and safefree(...) is never called.
Here is a in code example lines 1082 on.

My question is how I can mitigate these memory leaks? One idea I had was to store all malloc'd pointers to an array that is safefree'd on DESTROY or hooked into perl GC somehow .


Any guidance is helpful.

--yapgh
\ No newline at end of file +

+The city of Rome was built,
+with the first brick.
+

+

+

Alpha Release of new API

After a considerable amount of hacking and rewriting we have release the first development release of SDL perl on CPAN.
+
+

Overview of 2.3_1

In this version our goal was to tackle the proper allocations and destruction of SDL resources. We have accomplished this for all SDL Core structures. Moreover we have also improved the test suite and documentation considerably. Please read the CHANGELOG for a more detailed look.
+
+
+

Next steps


+--yapgh
+


+

\ No newline at end of file