I looked in detail in the DB access routines, and have resolved some of the questions in regard to the memory leaks. BrDbRevisions were create and allocate to a TObjeArray, but not delete after the 'best' ones was returned to the user. This is fixed. The routines though when picking out the data via the MySql calls do also generate root-object TMySqlRow .. that has no clear owner ship, and no clear place where to delete. (via GetMultiple ... for experts) These do also increase in magnitude. This nees more investigations, there may be similar problems for the DbRun and DbPass objects but I have not looke into this The new version is tagge 2-16-1 /fv ---------------------------------------------------------------- Flemming Videbaek Physics Department Brookhaven National Laboratory e-mail: videbaek@bnl.gov phone: 631-344-4106 _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Sun Apr 18 19:06:25 2004
This archive was generated by hypermail 2.1.8 : Sun Apr 18 2004 - 19:06:49 EDT