I've been using Metakit for a while now with a Windows and Windows CE data
entry application.
It has been working well...fast and robust for some fairly heavy duty
on-the-fly projections/selections and frequent commits.
However, I recently noticed "leaky" behavior on a limited-memory Windows CE
data recorder.
I ran it through CodeSnitch (Entrek Software, Inc) which indicated that the
app was riddled with small memory leaks. A majority of the reported leaks
have a fairly long call stack, but all end up pointing to strdup in:
void c4_StringArray::SetAt(int nIndex, const char* newElement)
{
char* s = (char*) _ptrs.GetAt(nIndex);
if (s && *s)
free(s);
_ptrs.SetAt(nIndex, newElement && *newElement? _strdup(newElement) : "");
}
The app RUNS, in fact it has been beta tested for a while now with no major
problems (http://www.fs.fed.us/fmsc/measure/cruising/fstallymeter/). If I
goofed anywhere with unicode/character conversions wouldn't the app bomb
noticeably?
Any ideas or clues to what I'm doing wrong? Anyone else using Metakit in
Windows CE software?
I'm using eVC++ 3.0 (MFC).
=====================================
Matt Oberle
_____________________________________________
Metakit mailing list - [EMAIL PROTECTED]
http://www.equi4.com/mailman/listinfo/metakit
