Smalltalk › Cincom › VisualWorks

vw 7.4.1 & OracleSession memory leak ?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Mark Plas

vw 7.4.1 & OracleSession memory leak ?

Hi,

We’re trying to upgrade from VW 7.2.1 to VW 7.4.1 and we’ve run into what we think is a memory leak. It seems that the ‘executor’ of an OracleSession indirectly holds on to its ‘to be executed’ OracleSession. It does this through the ‘session’ instance variable that has been added to the OracleBuffer class. Because of this reference of the executor to its executee, the OracleSessions don’t get garbage collected anymore. You now have to explicitly dismiss them.

The problem is that our application doesn’t explicitly close the sessions, it has always relied on the garbagecollector to do that. We now get the Oracle message “too many open cursors” fairly quickly.

Has anyone of you run into this problem and do you know whether their exists a bug fix/workaround for it ? (is it a bug?)

Thanks,

Mark

Reinout Heeck-2

Re: vw 7.4.1 & OracleSession memory leak ?

As it happens this just seems to be fixed in this weeks internal build
of Cincom, from the announcement:

Oracle Connect
51246 OracleBuffer inst var, session, prevents its
owning session from getting GC'd.

So, yes - it is a bug and will be fixed in 7.5.

R
-

Mark Plas wrote:

> Hi,
>
>
>
> We’re trying to upgrade from VW 7.2.1 to VW 7.4.1 and we’ve run into
> what we think is a memory leak. It seems that the ‘executor’ of an
> OracleSession indirectly holds on to its ‘to be executed’ OracleSession.
> It does this through the ‘session’ instance variable that has been added
> to the OracleBuffer class. Because of this reference of the executor to
> its executee, the OracleSessions don’t get garbage collected anymore.
> You now have to explicitly dismiss them.
>
>
>
> The problem is that our application doesn’t explicitly close the
> sessions, it has always relied on the garbagecollector to do that. We
> now get the Oracle message “too many open cursors” fairly quickly.
>
>
>
> Has anyone of you run into this problem and do you know whether their
> exists a bug fix/workaround for it ? (is it a bug?)
>
>
>
> Thanks,
>
> Mark
>

Mark Plas

RE: vw 7.4.1 & OracleSession memory leak ?

In reply to this post by Mark Plas

Thanks,

We're going to ask Cincom whether we can get the fix for this in our
7.4.1 version.

Mark

-----Original Message-----
From: Reinout Heeck [mailto:[hidden email]]
Sent: dinsdag 10 oktober 2006 12:24
To: vwnc-list
Subject: Re: vw 7.4.1 & OracleSession memory leak ?

As it happens this just seems to be fixed in this weeks internal build
of Cincom, from the announcement:

Oracle Connect
51246 OracleBuffer inst var, session, prevents its
owning session from getting GC'd.

So, yes - it is a bug and will be fixed in 7.5.

R
-

Mark Plas wrote:
> Hi,
>
>
>
> We're trying to upgrade from VW 7.2.1 to VW 7.4.1 and we've run into
> what we think is a memory leak. It seems that the 'executor' of an
> OracleSession indirectly holds on to its 'to be executed'
OracleSession.
> It does this through the 'session' instance variable that has been
added
> to the OracleBuffer class. Because of this reference of the executor
to

> its executee, the OracleSessions don't get garbage collected anymore.
> You now have to explicitly dismiss them.
>
>
>
> The problem is that our application doesn't explicitly close the
> sessions, it has always relied on the garbagecollector to do that. We
> now get the Oracle message "too many open cursors" fairly quickly.
>
>
>
> Has anyone of you run into this problem and do you know whether their
> exists a bug fix/workaround for it ? (is it a bug?)
>
>
>
> Thanks,
>
> Mark
>