Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 17127
  • 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

vManager Failed: Unexpected error ( Out of memory )

JennyYang
When I run following command to collect coverage  (There are 2000  vsof files)

emanager -coverage -vsof " ./covwork/irun/*/*.vsof " &

I got the Error: vManager Failed: Unexpected error

The reason is Out of memory .

When I run coverage follow. I always get 2 problems:

(1) vManager Failed: Unexpected error   ( Out of memory )

(2) If no error, it is very slow and will consume much of memory.

How to solve upper problems.

=================================================================================

Here are more log info:

Reading EManager configuration...
 

Doing EManager setup...
 

On-the-fly GC, current size is 2569369600 bytes (including 323404 known free)

Done - total size of reachable data is 79912192 bytes (plus 2467005536 free).
 

On-the-fly GC, current size is 3124511600 bytes (including 547645728 known free)

Done - total size of reachable data is 83085120 bytes (plus 3022911368 free).
 

On-the-fly GC, current size is 3198727704 bytes (including 628465380 known free)

Done - total size of reachable data is 85586128 bytes (plus 3093959788 free).
 

On-the-fly GC, current size is 3254023348 bytes (including 683430808 known free)

Done - total size of reachable data is 87813604 bytes (plus 3147439360 free).
 

Memory accounting is not enabled. Set the environment variable SPECMAN_MEMORY_ACCOUNTING to enable it
 

configuration options for: memory

        -automatic_gc_settings         =      STANDARD

        -optimal_process_size          =      3154116608

        -notify_gc_settings            =      FALSE

        -gc_threshold                  =   1393665248

        -gc_increment                  =  0

        -print_msg                     =  TRUE

        -print_otf_msg                 =   TRUE

        -retain_printed_structs        = TRUE

        -retain_trace_structs          = FALSE

        -max_retained_structs          =      0

        -disable_disk_based_gc         =     FALSE

        -max_size                      = 4273995775

        -absolute_max_size             =    4294967295

        -check_consistency             =    FALSE

        -print_debug_msgs              =   FALSE

        -expand_stack                  =   0
 

Please see chapter 'Specman Memory Consumption Is Too High' in the Specman documentation
 

**** Fatal error - leaving vManager:

Out of memory

vManager failed: Unexpected error
Parents

  • Hello Jenny.

    Enterprise Manager is very old now and loading a huge number of runs into it will be pushing its performance to the limit. You mentioned 2000 VSOFs, but is that one test per VSOF (should be OK) or many tests per VSOF? In fact the VSOF is only part of the picture, the size of the coverage model (*.ucm) files is also significant.

    You can run the tool in 64-bit mode using the -64 option to emanager; this might gain you some performance as well, because the garbage collection will be less frequent.

    What I would really recommend though is for you to consider switching to the new vManager Client-Server technology, as this is our new tool. It's going to replace emanager and has a much more capable GUI and can handle vastly more tests and coverage data. There is some change to the use model so I think you should talk to your local Cadence Applications Engineer for guidance. If you don't know who your AE is, send me  aprivate message indicating your contact details and which company you work for and I'll put you in touch with the local AE.

    Regards,

    Steve

Reply

  • Hello Jenny.

    Enterprise Manager is very old now and loading a huge number of runs into it will be pushing its performance to the limit. You mentioned 2000 VSOFs, but is that one test per VSOF (should be OK) or many tests per VSOF? In fact the VSOF is only part of the picture, the size of the coverage model (*.ucm) files is also significant.

    You can run the tool in 64-bit mode using the -64 option to emanager; this might gain you some performance as well, because the garbage collection will be less frequent.

    What I would really recommend though is for you to consider switching to the new vManager Client-Server technology, as this is our new tool. It's going to replace emanager and has a much more capable GUI and can handle vastly more tests and coverage data. There is some change to the use model so I think you should talk to your local Cadence Applications Engineer for guidance. If you don't know who your AE is, send me  aprivate message indicating your contact details and which company you work for and I'll put you in touch with the local AE.

    Regards,

    Steve

Children
No Data

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.