IDCS5 Mac - Massive memory leaks - Followup to previous discussion

Question

Hello Everyone:
   After some painful, tedious marching though the code on the Mac, I found something really, really strange.  The code seemed to be working fine, except when a couple of documents were added in the scan jobs.  I isolated one of the documents and removed each object on the page until I came across the object that, when scanned, caused InDesign to report the massive memory leaks.
   The object was a quarter-inch by quarter-inch overset text frame (that's .63 cm by .63 cm for those of you who are used to the more sensible metric system).  In the text frame was a single character, not normally visible when on the page.  According to the ASSERT dialog box that was thrown up on the screen when InDesign was shutting down, this little bitty object was the source of 104450 leaks amounting to between 38,000,000 abd 51,000,000 bytes in leaks.  Here's the code where the leaks must be coming from (and Dirk, I owe you a crow pie...as in I'm gonna have to eat crow...I use PMString for one small command in this snippet, but it seemed so much faster and simpler than what the examples in widestring.h were suggesting):
//  TI is TextIndex, assigned from a call to IMultiColumnTextFrame::TextStart()
//  TS is int32 assigned from a call to IMultiColumnTextFrame::TextSpan()
WideString Text;
TextIterator beginTextChunk(FrameTextModel,          TI );
TextIterator endTextChunk(   FrameTextModel, (TS + TI));
std::copy(beginTextChunk, endTextChunk, std::back_inserter(Text));
PMString PMText(Text);
std::string text = PMText.GetPlatformString();
IdentifyNamesInText(text);
This final function call could not have been the source of the problem because one of the steps I took in tracking down the problem was to put "return" as the first line in its implementation but the bug still occurred.

Answer 1

Hi, I don't know if this is relevant or not, particularly since we're on Windows and the problem you're seeing is on Mac.
One of our guys put in some code to workaround a problem which he encountered using std:;copy with TextIterators under VS2005 (so it would have been CS4)
/// Alternative to using std::copy to workaround issues using std::copy and TextIterator's in VS2005
inline void TextIteratorCopy( TextIterator& posBegin, TextIterator& posEnd, WideString& strDest )
    std::back_insert_iterator < WideString > posDest = std::back_inserter( strDest );
    for ( ; posBegin != posEnd; ++posDest, ++posBegin )
        *posDest = *posBegin;
that said, it might not affect you on the Mac, it might no longer be an issue with CS5 either.