06-26-2019 11:37 PM
I get the "The Vivado engine has run out of memory and must exit. Please contact technical support" error when asking the tool to report timing.
Running through the log it surprises me that the available amount of memory and CPU cores are so low.
get_param general.maxThreads returns 8
The issue looks similar to this one: https://forums.xilinx.com/t5/Design-Entry/The-Vivado-engine-has-run-out-of-memory-and-must-exit/td-p/704561 but if increasing the number of CPUs is the solution then
1. How do I do that?
2. Why and how is the tool not using the full amount of available CPU cores?
Alternatively, can increasing the max amount of memory to the JVM work? How can I do that in the TCL console?
The Details log is pasted below:
Xilinx Vivado v2019.1 (64-bit) [Major: 2019, Minor: 1] SW Build: 2552052 on Fri May 24 14:47:09 MDT 2019 IP Build: 2548770 on Fri May 24 18:01:18 MDT 2019 Process ID (PID): 26875 License: Customer Current time: Thu Jun 27 08:05:06 CEST 2019 Time zone: Central European Standard Time (Europe/Oslo) OS: Ubuntu OS Version: 5.0.7-050007-generic OS Architecture: amd64 Available processors (cores): 1 Display: :0 Screen size: 1920x1080 Screen resolution (DPI): 100 Available screens: 2 Available disk space: 131 GB Default font: family=Dialog,name=Dialog,style=plain,size=12 Java version: 9.0.4 64-bit Java home: /tools/Xilinx/Vivado/2019.1/tps/lnx64/jre9.0.4 Java executable location: /tools/Xilinx/Vivado/2019.1/tps/lnx64/jre9.0.4/bin/java Java initial memory (-Xms): 128 MB Java maximum memory (-Xmx): 2 GB User name: msd User home directory: /home/msd User working directory: User country: US User language: en User locale: en_US RDI_BASEROOT: /tools/Xilinx/Vivado HDI_APPROOT: /tools/Xilinx/Vivado/2019.1 RDI_DATADIR: /tools/Xilinx/Vivado/2019.1/data RDI_BINDIR: /tools/Xilinx/Vivado/2019.1/bin Vivado preferences file location: /home/msd/.Xilinx/Vivado/2019.1/vivado.xml Vivado preferences directory: /home/msd/.Xilinx/Vivado/2019.1/ Vivado layouts directory: /home/msd/.Xilinx/Vivado/2019.1/layouts PlanAhead jar file location: /tools/Xilinx/Vivado/2019.1/lib/classes/planAhead.jar Engine tmp dir: ./.Xil/Vivado-26875-msd-HP-ZBook-Studio-G3 Xilinx Environment Variables ---------------------------- XILINX: /tools/Xilinx/Vivado/2019.1/ids_lite/ISE XILINX_DSP: /tools/Xilinx/Vivado/2019.1/ids_lite/ISE XILINX_LICENSE_FILE: firstname.lastname@example.org XILINX_PLANAHEAD: /tools/Xilinx/Vivado/2019.1 XILINX_SDK: /tools/Xilinx/SDK/2019.1 XILINX_VIVADO: /tools/Xilinx/Vivado/2019.1 XILINX_VIVADO_HLS: /tools/Xilinx/Vivado/2019.1 GUI allocated memory: 409 MB GUI allocated memory percent used: 7.17% GUI peak memory used: 260 MB GUI total free memory: 2,846 MB GUI threads: "Attach Listener":RUNNABLE "AWT-EventQueue-1" in group "main":RUNNABLE "AWT-Shutdown":WAITING "AWT-XAWT":RUNNABLE "Batik CleanerThread" in group "main":WAITING "Common-Cleaner" in group "InnocuousThreadGroup":TIMED_WAITING "Finalizer":WAITING "HCindyUtils: Backup All Debug Files" in group "main":TIMED_WAITING "hw_ila_monitor" in group "main":WAITING "Image Animator 3" in group "main":TIMED_WAITING "Image Animator 3" in group "main":TIMED_WAITING "Java2D Disposer":WAITING "main" in group "main":TIMED_WAITING "Monitor HEventQueue" in group "main":TIMED_WAITING "Open Implemented Design" in group "main":RUNNABLE "Process Messages" in group "main":TIMED_WAITING "Reference Handler":RUNNABLE "Refresh Filesets Swing Worker" in group "main":TIMED_WAITING "RouteApi Init Delay Mediator Thread" in group "main":RUNNABLE "SyntheticaAnimation 25" in group "main":TIMED_WAITING "SyntheticaAnimation 50" in group "main":TIMED_WAITING "SyntheticaAnimation 50" in group "main":TIMED_WAITING "SyntheticaAnimation 70" in group "main":TIMED_WAITING "SyntheticaCleanerThread" in group "main":TIMED_WAITING "Thread-114" in group "main":RUNNABLE "Thread-1" in group "main":RUNNABLE "TimerQueue":TIMED_WAITING "Update Runs Swing Worker" in group "main":TIMED_WAITING GUI max memory: 3,066 MB Engine allocated memory: 3,028 MB Copyright 1986-2019 Xilinx, Inc. All Rights Reserved. The amount of used memory by Vivado GUI: 220 MB The % of memory used by Vivado GUI: 7.20% The amount of available memory (free memory plus never allocated memory): 2,845 MB The % of available memory (free memory plus never allocated memory): 92.80% Maximum (-Xmx) amount of memory that the JVM will attempt to use: 3,066 MB Engine heap size: 3,028 MB Current thread count: 28 Peak thread count: 30 Threads: --------------- HCindyUtils: Backup All Debug Files (TIMED_WAITING) RouteApi Init Delay Mediator Thread (RUNNABLE) Open Implemented Design (RUNNABLE) Thread-114 (RUNNABLE) SyntheticaAnimation 50 (TIMED_WAITING) Update Runs Swing Worker (TIMED_WAITING) Image Animator 3 (TIMED_WAITING) Image Animator 3 (TIMED_WAITING) hw_ila_monitor (WAITING) Refresh Filesets Swing Worker (TIMED_WAITING) SyntheticaAnimation 70 (TIMED_WAITING) SyntheticaAnimation 25 (TIMED_WAITING) SyntheticaAnimation 50 (TIMED_WAITING) Monitor HEventQueue (TIMED_WAITING) SyntheticaCleanerThread (TIMED_WAITING) Batik CleanerThread (WAITING) AWT-EventQueue-1 (RUNNABLE) AWT-Shutdown (WAITING) Process Messages (TIMED_WAITING) Thread-1 (RUNNABLE) TimerQueue (TIMED_WAITING) AWT-XAWT (RUNNABLE) Java2D Disposer (WAITING) Common-Cleaner (TIMED_WAITING) Attach Listener (RUNNABLE) Finalizer (WAITING) Reference Handler (RUNNABLE) main (TIMED_WAITING) Swing Workers: --------------- Process Messages (TIMED_WAITING) Monitor HEventQueue (TIMED_WAITING) Refresh Filesets Swing Worker (TIMED_WAITING) Update Runs Swing Worker (TIMED_WAITING) Open Implemented Design (RUNNABLE) ui.data.fed.d@11b3b005 RouteApi Init Delay Mediator Thread (RUNNABLE) Peak 'codeheap 'non-nmethods'' memory used: 1 MB Peak 'codeheap 'non-nmethods'' memory reserved: 2 MB Peak 'metaspace' memory used: 91 MB Peak 'metaspace' memory reserved: 99 MB Peak 'tenured gen' memory used: 213 MB Peak 'tenured gen' memory reserved: 355 MB Peak 'codeheap 'profiled nmethods'' memory used: 38 MB Peak 'codeheap 'profiled nmethods'' memory reserved: 38 MB Peak 'eden space' memory used: 48 MB Peak 'eden space' memory reserved: 48 MB Peak 'survivor space' memory used: 6 MB Peak 'survivor space' memory reserved: 6 MB Peak 'compressed class space' memory used: 12 MB Peak 'compressed class space' memory reserved: 14 MB Peak 'codeheap 'non-profiled nmethods'' memory used: 14 MB Peak 'codeheap 'non-profiled nmethods'' memory reserved: 14 MB
06-28-2019 01:51 AM
06-30-2019 09:29 PM
Hi @toxup_1 ,
First, you are using unsupported OS version for Vivado 2019.1. Please upgrade it to supported OS as shown below and then check you face the same issue or not.
You have already used command get_param general.maxThreads returns 8 which will use maximum 8 CPU cores in your design. And you will also see the info. messages in the log for specific phase like synth_design or opt_design.
Even after using supported OS, you face the same issue then try with this https://www.xilinx.com/support/answers/64434.html
06-30-2019 11:18 PM
I am using Ubuntu 18.04.2. What should I upgrade to? and will synth_design commands actually help with opening the synthesized design? Because the problem lies not with the actual synthesis, or implementation, but with opening the designs. That is when then tool crashes.
07-01-2019 01:33 AM
Hi @toxup_1 ,
Yes i have understood that the issue is while opening implemented design.
1. Do you face the same issue with every project design? or it is specific to a single project? Can you check it by running Vivado example design?
2. Run report_environment -file <filepath>/env.txt and provide that env.txt to evaluate environment of your machine.
3. As i mentioned in my previous email, use vivado -stack 2000 as mentioned in this AR https://www.xilinx.com/support/answers/64434.html and then run your project. Check you see the same issue or not.
07-01-2019 03:06 AM
Thank you for the quick reply. I have PMed you my env.txt. Increasing stack size does not work and the issue is not present when attempting to do the same with an example design (Microblaze base design).
07-01-2019 04:11 AM
Hi @toxup_1 ,
Okay, env. txt file is okay for now. And based on your last notes, it seems like the crash is project specific. Can you provide your archived project so i can reproduce this crash at my end while opening implemented design to investigate it further?
I have sent you ezmove ftp test package through which you can provide the archived project.
07-02-2019 11:16 PM
Hi @toxup_1 ,
Confirming this issue as machine specific as i am not able to reproduce it at my end.
You may try by reinstalling the Vivado in another directory which has all the permissions from administrator.
07-05-2019 12:38 AM
07-09-2019 02:02 AM
Update: I suspect there are multiple factors possibly triggering this memory issue. One of them is a width mismatch between Axi master bus width from the PS towards an AXI Interconnect. The default width is 128 bit when configuring the PS and if the Axi interconnect is configured for 32 bits, the memory issue will be present. I can now recreate the issue by switching between 128 and 32 bit width.
A slightly more complex design of mine will have the memory issue despite configuring the data width for 32 bits. I am continuing trying to isolate the causes.