X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pages%2Fblog-0020.html-inc;h=6e3de5785ff63fe5d5bee4838b6f576db4c2c038;hb=e785862422f3e827a242fc244bd57b23443887ce;hp=da0846f7e72f96b7501e8b50a220fb61a9da74a9;hpb=6b8e717c0e647220ce022cd254e7a248f8c8bbc6;p=sdlgit%2FSDL-Site.git diff --git a/pages/blog-0020.html-inc b/pages/blog-0020.html-inc index da0846f..6e3de57 100644 --- a/pages/blog-0020.html-inc +++ b/pages/blog-0020.html-inc @@ -1,6 +1,21 @@

-Catching memory leaks in XS +A summer of possibilities (SDL_perl and GSOC 2010 )

-
 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 +

GSOC 2010


+

As many of the readers must know The Perl Foundation has been accepted for the GSOC 2010 program. There are several SDL_perl mentors involved in it too. Right now we are accepting student applications.


+
+Process to Apply
+


+
+

Ideas


+

Here are some ideas for SDL perl but we happily accepted student ideas.
+ Make a student wiki page on this site of your ideas! We look forward to helping you guys with your ideas :)


+
+--yapgh
+


+

\ No newline at end of file