[Oorexx-bugs] [ oorexx-Bugs-2855167 ] About Memory leaks (see issue ID: 2833447)

[SourceForge.net <no...@so...>]

Bugs item #2855167, was opened at 2009-09-09 09:14
Message generated for change (Settings changed) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2855167&group_id=119701

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: APIs
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Laurent Crepel (lcrepel)
>Assigned to: Rick McGuire (bigrixx)
Summary: About Memory leaks (see issue ID: 2833447)

Initial Comment:
The version i have installed is the latest version V4.0 ooRexx-4.0.0.i586.exe available.
The platform i used is WinXP-32 bit.

To use the following sample CvHello set the Hello.rex in C:\, then run CvHello.
I have engage a purify integration and detects some leaks on RexxSetProcessMessages and RexxPullQueue.
You can see the report in attachment. I think this is this issue that make troubles on our application.
Could you say to me if it is a real bug?

Thanks in advance,

Laurent CREPEL.


----------------------------------------------------------------------

>Comment By: Rick McGuire (bigrixx)
Date: 2009-09-09 09:33

Message:
Your purify data cannot be accurate with respect to RexxPullFromQueue and
RexxSetProcessMessages.  The RexxSetProcessMessages consists of the
following code: 

BOOL APIENTRY RexxSetProcessMessages(BOOL onoff)
{
   return TRUE;
}

It is just a stubbed out API that always returns TRUE in 4.0.  I cannot
cause a memory leak because is does not allocated any memory.  

Additionally, RexxPullFromQueue() got a lot of attention in the beta
period, and I'm 100% certain that it does not leak memory....a fact I
verified the last time you opened this issue. 

However, even more importantly, neither of these APIs are even called by
the sample you provided.  Additionally, running this program shows no sign
of a memory leak in the interpreter.  The memory of both the client and the
rxapi process stabilize at a fixed value, displaying exactly the behavior
we would expect to see in normal operations. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2855167&group_id=119701