IC5033/Assura on Linux do not release memory.

Discussion in 'Cadence' started by Raghavendra, Dec 21, 2006.

  1. Raghavendra

    Raghavendra Guest

    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...ry+leak+cadence&rnum=3&hl=en#de5232c5686d9524

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

    Any thoughts?

    Thanks!!
    Raghavendra
     
    Raghavendra, Dec 21, 2006
    #1
  2. Raghavendra

    Poojan Wagh Guest

    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.
     
    Poojan Wagh, Dec 30, 2006
    #2
  3. Raghavendra

    Raghavendra Guest

    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
     
    Raghavendra, Jan 1, 2007
    #3
  4. 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, Jan 9, 2007
    #4
  5. Raghavendra

    Tim Guest

    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
     
    Tim, Jan 10, 2007
    #5
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.