We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

Page Bookmarked

AR# 55815

Vivado - GUI does not free up memory from opening a Synthesized Design after closing it


Vivado does not free up the memory used to open a Synthesized/Implemented Design after I close it.

The memory usage does not go down in the task manager after I close the design in the GUI.

Is this a memory leak?


This situation is specific to Windows 7.

When you close the design view, the memory is released, however the OS does not "collect" it for use until there is a need for that memory.

It stays available for the Vivado application until you hit a point where the memory is absolutely needed (if you max out the memory resources).

The way Vivado is currently structured, the Synthesis/Implementation runs create a separate call of "vivado.exe", so it does not use the memory available to the first instance of "vivado.exe" (unless needed), as this instance is used for GUI operations.
AR# 55815
Date 12/10/2014
Status Active
Type General Article
  • Vivado Design Suite - 2012.4
  • Vivado Design Suite - 2013.1