After installing Vivado 2014.x on a Windows 7 machine, Vivado License Manager (VLM) crashes on opening.
A hs_err log file is created.
The top portion of the file reads as follows:
# A fatal error has been detected by the Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fef4cd9b5b, pid=4540, tid=1932
# JRE version: Java(TM) SE Runtime Environment (7.0_40-b43) (build 1.7.0_40-b43)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.0-b56 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [libXil_lmgr11.dll+0xa9b5b]
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
# If you would like to submit a bug report, please visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
--------------- T H R E A D ---------------
Current thread (0x000000000ac41000): JavaThread "SwingWorker-pool-2-thread-1" daemon [_thread_in_native, id=1932, stack(0x000000000ec80000,0x000000000ed80000)]
siginfo: ExceptionCode=0xc0000005, reading address 0x0000000000000414
This reported crash happens due to an incorrect value of the LM_LICENSE_FILE variable.
For example, The fatal error occurs with the following LM_LICENSE_FILE variable value:
Notice that the different license locations are delimited with a comma.
Commas should only be used to delimit the three servers of a 3-redundant server setup.
Otherwise license locations should be separated with a semicolon (Windows) or a colon (Linux).
By changing the commas to semicolons, the fatal error is resolved and licensing works successfully.