Since the situation is deterministic, try removing FastMM and
reverting to the Delphi native memory manager, and see if the problem
goes away. If the problem stays, it's not FastMM. If the problem
goes away, it probably is (unless it's some sort of whacky bad
pointer that Delphi's MM can handle but FastMM cannot, but that's an
unlikely case).
We have been using Stefan Heymann's XML parser (see
www.destructor.de) and it has been very effective, don't know if
it'll meet your needs though.
At 06:15 AM 6/13/2009, Paulo Silva | Critical Software 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 -> Delphi@elists.org
http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
Regards,
Sid Gudes
PIA Systems Corporation
sid.gu...@piasystems.com
_______________________________________________
Delphi mailing list -> Delphi@elists.org
http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
