I would recommend you stick to FastMM (it's the one used by default by the latest Delphi editions). You might want to turn on the memory leak checks and the other options in FastMM. D5 and D7 has been very reliable in my experience, and I suspect it's rather down to double freeing or something like that. Anyway, FastMM's logging/reporting options should lead you to the cause.
Best regards, Laurent On Sat, Jun 13, 2009 at 12:15 PM, Paulo Silva | Critical Software < [email protected]> wrote: > > > Hi to all: > > We have been authors and are supporting a huge LOB application for the > Paper > and Mill industry since 1998, meanwhile migrated to Delphi 7. Some Java SOA > data layer is being used now and Delphi is still being used for client data > presentation (consuming Web Services) with great results (client datasets > are being used). > > > > Recently we have started having some Access Violations (after creating some > forms and closing one of them - the situation is deterministic / can be > reproduced) and we suspect that this is some kind of memory management > problem (or even the native SOAP parser that has lots of reported issues > (inclusively it does not support namespaces in the SOAP messages). > > > > Can anyone suggest: > > - A memory manager (free if possible) - we are using FastMM. > > - An alternate parser for replacement of Delphi native one? > > > > Any links and suggestions would be very much appreciated and even more if > you are already using them without problems for some time. > > > > Thanks in advance, > > Paulo Silva - Critical Software SA > > _______________________________________________ > Delphi mailing list -> [email protected] > http://lists.elists.org/cgi-bin/mailman/listinfo/delphi > _______________________________________________ Delphi mailing list -> [email protected] http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
