TrackAllocation asserts: why? How to get rid of it?

Question

I am having trouble with this kind of assert with InDesign CS5.5. Here at my company we developed a plug-in that exists since InDesign 2.0 and CS3, running without any problem other than bugs within itself. But since we managed to get the Debug version of InDesign CS5.5 to track our code, I got HUNDRENDS of this warning. Most of it related to K2 collections and iteration, like:

- when I duplicate a AttributeBossList;

- when I use a K2Vector with some datatypes;

- when I use the IParcelList::iterator;

- when I use the IIntegratorTarget::GetTarget method;

- among other cases.

I tried to reduce the messages, by replacing K2Vector with std::vector, but that wasn't enough. I suspect it is caused by some mixed memory reallocation and the InDesign debug tracker got lost somehow, but have no clue of WHY. Because of that huge amount of asserts, the debuging process became quite useless

Does anyone know WHAT should a look for, and where, to see WHY is this hapenning?

Dirk Becker · Accepted Answer

There is a special case in the C++ standard: the linker handles overloading of operator delete, standard library provides a "weak" symbol for fallback. Your project is missing some SDK library. Don't ask me which, compare the linker command in the build log to that of a working SDK plugin.

Dirk

adobedeveloper@mundiware. · Answer

I think I got around this. Looks like the delete operator is not properly overloaded by the InDesign SDK at my plugin compilation (don't know why), and so it wasn't calling the method K2Memory::RTLCompatibleDeleteDelegate. The solution I found out is to call myself this method, to delete pointers returned to me by other InDesign Plugins or core library (PMRuntime.lib)

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.