In Vivado 2014.2 I am receiving an intermittent java.lang.ArrayIndexOutOfBoundsException.
The console shows an error like the below:
reset_run synth_1
ERROR: [Vivado 12-106] *** Exception: java.lang.ArrayIndexOutOfBoundsException: 3 >= 3 (See C:/Users/Administrator/AppData/Roaming/Xilinx/Vivado/vivado_pid223456.debug)
ERROR: [Vivado 12-106] *** Exception: java.lang.ArrayIndexOutOfBoundsException: 2 >= 2 (See C:/Users/Administrator/AppData/Roaming/Xilinx/Vivado/vivado_pid223456.debug)
ERROR: [Common 17-39] 'reset_run' failed due to earlier errors.
launch_runs synth_1
The debug file contains text similar to the following:
#-------------------------------------------------------------------------------
# Vivado v2014.2 (64-bit)
# SW Build 928826 on Thu Jun 5 18:17:50 MDT 2014
# Current time: 6/19/14 5:42:24 PM
# Process ID: 5632
# Platform: Windows
#
# This file is an indication that an internal application error occurred.
# This information is useful for debugging. Please open a case with Xilinx
# Technical Support with this file and a testcase attached.
#-------------------------------------------------------------------------------
6/17/14 3:43:24 PM
java.lang.ArrayIndexOutOfBoundsException: 0 >= 0
at java.util.Vector.elementAt(Vector.java:470)
at javax.swing.tree.DefaultMutableTreeNode.getChildAt(DefaultMutableTreeNode.java:243)
at javax.swing.tree.VariableHeightLayoutCache.treeNodesRemoved(VariableHeightLayoutCache.java:560)
at javax.swing.plaf.basic.BasicTreeUI$Handler.treeNodesRemoved(BasicTreeUI.java:3906)
at javax.swing.tree.DefaultTreeModel.fireTreeNodesRemoved(DefaultTreeModel.java:548)
at javax.swing.tree.DefaultTreeModel.nodesWereRemoved(DefaultTreeModel.java:328)
at javax.swing.tree.DefaultTreeModel.removeNodeFromParent(DefaultTreeModel.java:262)
at ui.views.q.b.k.c(SourceFile:836)
at ui.views.q.b.k.b(SourceFile:827)
at ui.views.q.b.k.b(SourceFile:873)
at ui.views.q.b.k.JO(SourceFile:890)
at ui.views.q.b.q.JO(SourceFile:755)
at ui.views.q.b.Y.a(SourceFile:166)
at ui.frmwork.a.j.d(SourceFile:41)
at ui.frmwork.HTclEventBroker.n(SourceFile:256)
at ui.frmwork.t.run(SourceFile:329)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:241)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
at ui.frmwork.a.e.dispatchEvent(SourceFile:75)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91
The Messages view is getting out of sync and is not able to display all messages.
As the issue is only affecting the Messages view, it is safe to continue using Vivado.
Keep in mind though that the Message View will not be able to show the messages correctly.
Closing and reopening the project will usually resolve this issue.
This issue is fixed in Vivado 2014.3
| AR# 63322 | |
|---|---|
| 日期 | 01/23/2015 |
| 状态 | Archive |
| Type | 已知问题 |
| Tools | |