First off, my apologies if this post is in the wrong area. I'm using Progress

9.1D WebSpeed. We're posting XML to a WebSpeed procedure and then using the

WEB-CONTEXT:X-DOCUMENT handle to read the XML document that was posted and

perform various functions returning an XML result (t's kinda a Progress XML

Service). In the process of doing this we leaking memory somewhere. I've

been doing some prototyping just to see if i can reproduce the error in a simplified

scenario. A question of some controversy thus far is whether the approach

seen in the code below will leak memory or wether in general it's a bad idea

DEFINE TEMP-TABLE ttTest NO-UNDO

FIELD hTmp AS WIDGET.

Def var iCount as int.

DO iCount = 1 TO 1000:

RUN CreateRecord.

RUN DeleteRecord.

END.

PROCEDURE CreateRecord:

CREATE ttTest.

CREATE X-NODEREF ttTest.hTmp.

END PROCEDURE.

PROCEDURE DeleteRecord:

FIND FIRST ttTest EXCLUSIVE-LOCK.

DELETE WIDGET ttTest.hTmp.

DELETE ttTest.

END PROCEDURE.

I'd appreciate any ideas that you have. In case it helps the OS is IBM AIX.

Also we're using the DOM and not SAX and I am aware of KBase P9849 which suggests

that the DOM leaks memory in IBM AIX and suggests SAX as an alternative. If

you have any input on SAX performance verses the DOM or any insight on the

pros and cons (other than the fact that the DOM leaks memory on AIX) that would

also be appreciated.

Many thanks in advance.

Everett