email received by PK:
I discovered an issue recently where the Combo AU plug-in causes an assertion failure when it is loaded by a debug build of Digital Performer. There are two ways to provoke this assertion failure: Either the plug-in has written outside a memory block or it has deallocated a memory block that it didn't allocate.
I did some testing described in Apple Technical Note TN2204: It passes auval, and it passes the memory scribble and guard malloc tests. When I run leaks on auval while it's testing the plug-in, it does show that it's leaking memory. Based on those results, our DP developers explained that the plug-in is probably deallocating a memory block that it didn't allocate.
I know that these plug-ins haven't been updated in a while, but I did want to send you this information in case it's useful to you. There is no apparent problem when Combo is loaded by the shipping (non-debug) build of Digital Performer, so an end user would probably never notice a problem. Please let me know if you require any further information.
Quality Assurance Technician
Log in to post a comment.