IC5033/Assura on Linux do not release memory.

[Raghavendra]

Hello Experts,

We are facing an interesting problem. IC5033 and Assua (DRC/LVS and
extraction) tools do not release memory even after the user closes the
applications. This happens very consistently on Fedora4 and on Centos
4.4. I know fedora is not supported by cadence. I am surprised to see
this problem.

Is this a known problem? Is there a patch for this?

I did look through the archives and found this:

http://groups.google.com/group/comp.cad.cadence/browse_thread/thread/2614d55abdf9c11f/de5232c5686d9524?lnk=st&q=memory+leak+cadence&rnum=3&hl=en#de5232c5686d9524

This is not exactly the same problem...but sounds similar.

Any thoughts?

Thanks!!
Raghavendra

 

[Poojan Wagh]

This is a known problem with Assura. I think a PCR was submitted for
it, but I don't know what came of it. From what I recall, it only
affects the GUI interface, not command-line Assura.

On Dec 20, 11:16 pm, "Raghavendra" <rag...@gmail.com> wrote:

Hello Experts,

We are facing an interesting problem. IC5033 and Assua (DRC/LVS and
extraction) tools do not release memory even after the user closes the
applications. This happens very consistently on Fedora4 and on Centos
4.4. I know fedora is not supported by cadence. I am surprised to see
this problem.

Is this a known problem? Is there a patch for this?

I did look through the archives and found this:

http://groups.google.com/group/comp.cad.cadence/browse_thread/thread/...

This is not exactly the same problem...but sounds similar.

Any thoughts?

Thanks!!
Raghavendra

 

[Raghavendra]

Poojan, Thanks for the reply.

Does any one else know the details about the PCR for this problem? Any
pointers would be useful.

Thanks!
-Raghavendra

Poojan Wagh wrote:

This is a known problem with Assura. I think a PCR was submitted for
it, but I don't know what came of it. From what I recall, it only
affects the GUI interface, not command-line Assura.

On Dec 20, 11:16 pm, "Raghavendra" <rag...@gmail.com> wrote:
Hello Experts,

We are facing an interesting problem. IC5033 and Assua (DRC/LVS and
extraction) tools do not release memory even after the user closes the
applications. This happens very consistently on Fedora4 and on Centos
4.4. I know fedora is not supported by cadence. I am surprised to see
this problem.

Is this a known problem? Is there a patch for this?

I did look through the archives and found this:

http://groups.google.com/group/comp.cad.cadence/browse_thread/thread/...

This is not exactly the same problem...but sounds similar.

Any thoughts?

Thanks!!
Raghavendra

 

[Andrew Beckett]

On 1 Jan 2007 13:18:10 -0800, "Raghavendra" <ragkul@gmail.com> wrote:

Poojan, Thanks for the reply.

Does any one else know the details about the PCR for this problem? Any
pointers would be useful.

Thanks!
-Raghavendra

If you've exited DFII, and the memory is not released, then that's an OS bug.
You should be aware that on Linux, "top" tends to give a rather misleading
report of what memory is "free" .

There was a problem with running multiple Assura runs in the same session,
and a memory release related to that, but I think that was fixed a number of
Assura versions ago...

Andrew.
--
Andrew Beckett
Principal European Technology Leader
Cadence Design Systems, UK.

 

[Tim]

We had a problem in Solaris with the Virtual Memory filling up but it
would release when exiting and restarting. This was improved in the 314
version, it still will fill the VM but it now takes more runs.

The 314 version does have a problem with leaving avxp processes running
which will consume the CPU. This is supposed to be fixed in the 315
version.

Tim