Stats

  • Locked Locked
  • Replies 10
  • Subscribers 125
  • Views 20702
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Virtuoso continues to crash

Miguel V

Hi,

I have a colleague who keeps having issues with virtuoso unexpectedly crashing whenever she tries to open a layout in either read or edit mode.  Some cells are fine, but there are some that crash every single time, even tried to jump to a different server or create a new workarea.  I've tried to have her copy the layout in question but the crashing still happens.  Also, it doesn't matter what version of Virtuoso we use, the result is always the same.  

Parents

  • Hi Andrew,

    I'm coming back to this.  The error is popping up again and this time when I run oaScan, I get the following error and the repair also terminates with a SIGSEGV error just as cadence outputs when it crashes...

    Running: oaScan -lib <the-library> -repair
    Started: Mon Mar 30 10:53:18 2020 (Hostname: <server>)
    Cellview <library>/<cell-name>/layout_test_new 'maskLayout':
    - data model 0 saved by an app compiled against 22.60.007 running 22.60.007
    - platform linux_rhel60_64 gcc_6.3.0
    FIXED REPAIR-93: Repaired the inconsistent appData reference on a inst.
    FIXED REPAIR-93: Repaired the inconsistent appData reference on a shape.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig1 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig1 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig1 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig1 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    An internal error SIGSEGV has occurred and oaScan must exit.
    Note that some databases may not have been processed.
    Report this error through your support channel.

    -Miguel

Reply

  • Hi Andrew,

    I'm coming back to this.  The error is popping up again and this time when I run oaScan, I get the following error and the repair also terminates with a SIGSEGV error just as cadence outputs when it crashes...

    Running: oaScan -lib <the-library> -repair
    Started: Mon Mar 30 10:53:18 2020 (Hostname: <server>)
    Cellview <library>/<cell-name>/layout_test_new 'maskLayout':
    - data model 0 saved by an app compiled against 22.60.007 running 22.60.007
    - platform linux_rhel60_64 gcc_6.3.0
    FIXED REPAIR-93: Repaired the inconsistent appData reference on a inst.
    FIXED REPAIR-93: Repaired the inconsistent appData reference on a shape.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig1 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig1 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig1 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig1 of marker on inst.
    FIXED REPAIR-184: Repaired the inconsistent InterPointerAppDef leVioFig2 of marker on inst.
    An internal error SIGSEGV has occurred and oaScan must exit.
    Note that some databases may not have been processed.
    Report this error through your support channel.

    -Miguel

Children
  • in reply to Miguel V

    Hi Miguel,

    Apologies for this being blocked as spam initially - the repeated text in the message is what was used to indicate that it might be spam. Obviously this wasn't, which is why it comes to moderation. Anyway, if you're using a current oaScan (say, from the latest IC618/ICADVM181 ISR, ISR10), then please contact customer support, as the message suggests.

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    Yes, I figured that's what happened since I know it wasn't "offensive".  It's weird, I deleted the cell causing that issue and ran oaScan again and it completed without the SIGSEGV error.  The issue now is when my coworkers makes a few edits and goes to save, cadence crashes yet again.  She can open it back up just fine and make more edits, the issue is the crash every time she goes to save it.  She's working remotely through VPN so not sure if that is somehow contributing to the problem because in her words, this doesn't happen when she works from her office.

  • in reply to Miguel V

    I rather doubt the VPN has anything to do with it.

    Which IC sub-version are you using, and what does "oaScan -version" report? I found some recent fixes related to InterPointerAppDef (this might not be the issue, but they are also reported in your log) but let's see...

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    We are using IC6.1.8 64b.83. 

    "oaScan -version" reports the following:

    Tool: oaScan oaScan_p047 (22.50)

  • in reply to Miguel V

    Hi Miguel,

    You have the base release of IC618 there (and the oaScan that comes with it) - this is 18 months old. I'd suggest first starting by getting IC618 ISR10 installed (the latest version on downloads.cadence.com) and seeing whether oaScan from that build works - you may need to use that subversion too for editing if it fixes the underlying data corruption problem.

    If that doesn't fix it, you'll really need to contact customer support.

    Regards,

    Andrew.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.