"...found a potential memory leak" error in SL log

sharonc · Post by **sharonc** » 23 Feb 2011 11:29

Hi,
I was wondering if anyone has encountered "potential memory leak" error in their SL logs.
This message constantly gets written to the logs every couple of minutes... here is an extract of it:

0224 09:24:59.14 SL: PP_OUT_exec: DB_ExecSelect(rowBuffer=1053a8, rowbufNumberOfAllocs=11) - found a potential memory leak
0224 09:24:59.14 SL: PP_OUT_exec: FreeSelectBuffer(rowBuffer=1053a8, rowbufNumberOfAllocs=11) - found a potential memory leak
0224 09:24:59.15 SL: PP_OUT_exec: FreeSelectBuffer(rowBuffer=1053a8, rowbufNumberOfAllocs=11) - found a potential memory leak

This has happened twice this year. We stopped and started the DBs and Control-M EM and Server last time, and this seems to have stopped the error messages appearing. But now, it's back again.

We run Control-M version 6.3.01 fixpack 4 on Solaris platform.

Any info on why this happens would be appreciated.

Thanks.

Sharon

Taouche · Post by **Taouche** » 30 Sep 2011 12:26

Hi,

i didn't want to open a new topic, i have exactly the same problem.
In the beginning, i have a job waiting for a prerequisite condition from a previous job.
This condition was posted, but the next job didn't want to run.

After some researchs i have found many SL logs with this message :

GM_SHOUT_send_shout: ExecSelect(rowBuffer=728d0, rowbufNumberOfAllocs=44) - found a potential memory leak

Someone have a solution or have the same issue ?
Thanks for your help.

Regards