[JWplugins] Memory leak tests
Jari Williamsson
jari.williamsson at mailbox.swipnet.se
Thu Apr 4 13:52:04 CEST 2013
Hello all!
As you might now, my plug-ins are based on my own PDK Framework (which
gives me a much nicer programming environment than doing the C++
development directly towards the Finale PDK).
However, since I started with the PDK Framework 2.5 years ago, my main
focus has been to create new plug-ins and add more functionality. And at
the start, my plug-in projects were quite small, and hunting for "tiny"
memory leaks in the plug-ins was not worth the time.
Since then, the plug-in projects has grown quite considerably in size
and complexity, and the demands for real memory leak testing has become
more and more important. (A memory leak of 20 bytes is "nothing", but if
that code is executed 1,000nds of times during the plug-in processing,
it will at some point start to hurt performance.)
Yesterday, I started to do proper tests of the plug-ins for memory leaks
and I have found some places both in the PDK Framework and in the
plug-ins that I have now fixed. All plug-in updates that appear from now
on should be properly tested for memory leaks (meaning better overall
stability if you use the plug-ins many many many times without
restarting Finale).
Best regards,
Jari Williamsson
More information about the JWplugins
mailing list