UPGRADE YOUR BROWSER

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!

Reply

Internal Exception Error in 2017.1

Highlighted
Observer
Posts: 12
Registered: ‎09-22-2016

Internal Exception Error in 2017.1

Hi,

 

We downloaded the new 2017.1 Vivado (Windows 64-bit).  

 

We then started re-building the IP cores for some current projects to use 2017.1

 

Unfortunately, we received a popup message:

"An internal exception has been detected.  Vivado may be in an unstable state.  Would you like to exit now. " 

 

Pressing the "Details" button gave the following.   Hope that this helps.

 

#-------------------------------------------------------------------------------
# Vivado v2017.1 (64-bit)
# SW Build 1846317 on Fri Apr 14 18:55:03 MDT 2017
# IP Build 1846188 on Fri Apr 14 20:52:08 MDT 2017
# Current time: 4/20/17 11:00:20 AM EDT
# Process ID: 11036
# OS: Windows 10
#
# This report 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.
#-------------------------------------------------------------------------------
java.lang.ArrayIndexOutOfBoundsException: 1
at com.jidesoft.plaf.basic.BasicJideTabbedPaneUI.calculateTabWidth(Unknown Source)
at com.jidesoft.plaf.basic.BasicJideTabbedPaneUI$TabbedPaneScrollLayout.calculateTabRects(Unknown Source)
at com.jidesoft.plaf.basic.BasicJideTabbedPaneUI$TabbedPaneLayout.calculateLayoutInfo(Unknown Source)
at com.jidesoft.plaf.basic.BasicJideTabbedPaneUI.ensureCurrentLayout(Unknown Source)
at com.jidesoft.plaf.basic.BasicJideTabbedPaneUI.getTabBounds(Unknown Source)
at javax.swing.JTabbedPane.getBoundsAt(JTabbedPane.java:1289)
at javax.swing.JTabbedPane.setBackgroundAt(JTabbedPane.java:1466)
at com.jidesoft.document.TdiGroup.updateTitle(Unknown Source)
at com.jidesoft.document.DocumentPane.a(Unknown Source)
at com.jidesoft.document.DocumentPane.updateDocument(Unknown Source)
at com.jidesoft.document.DocumentPane.propertyChange(Unknown Source)
at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263)
at com.jidesoft.document.DocumentComponent.firePropertyChange(Unknown Source)
at com.jidesoft.document.DocumentComponent.setIcon(Unknown Source)
at ui.views.d.A.eXx(SourceFile:335)
at ui.views.d.b.ahH(SourceFile:940)
at ui.views.d.A.ahH(SourceFile:119)
at ui.views.R.M.convert(SourceFile:1317)
at com.jidesoft.swing.JideTabbedPane.getDisplayTitleAt(Unknown Source)
at com.jidesoft.plaf.basic.BasicJideTabbedPaneUI.getCurrentDisplayTitleAt(Unknown Source)
at com.jidesoft.plaf.basic.BasicJideTabbedPaneUI$ContainerHandler.componentAdded(Unknown Source)
at java.awt.AWTEventMulticaster.componentAdded(AWTEventMulticaster.java:200)
at java.awt.AWTEventMulticaster.componentAdded(AWTEventMulticaster.java:199)
at java.awt.Container.processContainerEvent(Container.java:2262)
at java.awt.Container.processEvent(Container.java:2233)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2294)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.Container.addImpl(Container.java:1138)
at javax.swing.JTabbedPane.insertTab(JTabbedPane.java:724)
at com.jidesoft.swing.JideTabbedPane.insertTab(Unknown Source)
at javax.swing.JTabbedPane.addTab(JTabbedPane.java:767)
at com.jidesoft.document.TdiGroup.addDocument(Unknown Source)
at com.jidesoft.document.DocumentPane.a(Unknown Source)
at com.jidesoft.document.DocumentPane.openDocument(Unknown Source)
at com.jidesoft.document.DocumentPane.openDocument(Unknown Source)
at ui.views.R.a.a(SourceFile:1496)
at ui.views.R.a.a(SourceFile:1458)
at ui.views.R.B.actionPerformed(SourceFile:1096)
at ui.views.R.C.actionPerformed(SourceFile:1116)
at ui.views.ax.ePJ(SourceFile:297)
at ui.views.ac.r(SourceFile:1329)
at ui.views.av.r(SourceFile:235)
at ui.views.av.ePw(SourceFile:224)
at ui.views.av.c(SourceFile:118)
at ui.views.aw.f(SourceFile:149)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at ui.frmwork.a.d.dispatchEvent(SourceFile:75)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Moderator
Posts: 457
Registered: ‎09-15-2016

Re: Internal Exception Error in 2017.1

Hi @engeltronics.com,

 

When you say 'rebuilding the IP cores', does this project run in VIvado 2016.4 perfectly with the same design settings? If yes, can you please share your design/project for further analysis?

 

And does the tool crash after the warning? Are you able to continue with the project runs even after the message is displayed?

 

Regards,
Prathik
-----------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helps to resolve your query.
Helpful answer -> Give Kudos
-----------------------------------------------------------------------------------------------

Moderator
Posts: 1,309
Registered: ‎07-21-2014

Re: Internal Exception Error in 2017.1

@engeltronics.com

 

Can you share the generated log and check the install.log(check install location) file for any warnings or errors?

Also, can you test any 2016.4 example design in 2017.1 to check whether this is a design issues or machine specific issue?

 

Thanks,
Anusheel
-----------------------------------------------------------------------------------------------
Search for documents/answer records related to your device and tool before posting query on forums.
Search related forums and make sure your query is not repeated.

Please mark the post as an answer "Accept as solution" in case it helps to resolve your query.
Helpful answer -> Give Kudos
-----------------------------------------------------------------------------------------------

Observer
Posts: 12
Registered: ‎09-22-2016

Re: Internal Exception Error in 2017.1

Hi,

 

The design that failed 2017.1 compiles/implements/downloads correctly in 2016.4    - and no project issues have been encountered in 2016.4

 

Of course it was necessary to rebuild the DPRAMs, ILA and XADC as part of transferring the design to 2017.1

 

Unfortunately we are not able to provide the project (in 2016.4 or 2017.1) since it contains proprietary code.

 

The error log was provide in the original post.    Is this of any assistance ?

 

Thanks.

Visitor
Posts: 11
Registered: ‎01-17-2015

Re: Internal Exception Error in 2017.1

I have a similar problem.. That is so annoying..

Please share your ideas.. I have attached the log file..

I think this is related with using a core that had been generated before in another project..

But this is just an estimation..

#-------------------------------------------------------------------------------
# Vivado v2017.1 (64-bit)
# SW Build 1846317 on Fri Apr 14 18:54:47 MDT 2017
# IP Build 1846188 on Fri Apr 14 20:52:08 MDT 2017
# Current time: 6/9/17 10:27:57 PM EEST
# Process ID: 3069
# OS: Linux
#
# This report 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.
#-------------------------------------------------------------------------------
java.lang.UnsupportedOperationException: This is supposed to be overridden by subclasses.
    at com.google.protobuf.GeneratedMessage.getUnknownFields(GeneratedMessage.java:262)
    at ui.data.device.d.l.getSerializedSize(SourceFile:8409)
    at com.google.protobuf.AbstractMessageLite.toByteArray(AbstractMessageLite.java:67)
    at ui.data.device.H.axB(SourceFile:531)
    at ui.data.device.H.axy(SourceFile:454)
    at ui.data.device.H.axl(SourceFile:276)
    at ui.data.device.E.j(SourceFile:122)
    at ui.data.device.E.<init>(SourceFile:63)
    at ui.data.ah.lN(SourceFile:1347)
    at ui.data.ah.cP(SourceFile:217)
    at ui.data.ah.<init>(SourceFile:146)
    at ui.data.aW.<init>(SourceFile:38)
    at ui.project.a.edJ(SourceFile:252)
    at ui.project.a.init(SourceFile:236)
    at ui.project.r.a(SourceFile:1080)
    at ui.frmwork.a.k.d(SourceFile:41)
    at ui.frmwork.HTclEventBroker.i(SourceFile:259)
    at ui.frmwork.HTclEventBroker.fireTclEvent(SourceFile:330)

Moderator
Posts: 1,309
Registered: ‎07-21-2014

Re: Internal Exception Error in 2017.1

@akcaylatif

 

Both crash stacks looks different to me. Is there any possibility of sharing the test case for us to reproduce the issue?

 

Thanks,
Anusheel
-----------------------------------------------------------------------------------------------
Search for documents/answer records related to your device and tool before posting query on forums.
Search related forums and make sure your query is not repeated.

Please mark the post as an answer "Accept as solution" in case it helps to resolve your query.
Helpful answer -> Give Kudos
-----------------------------------------------------------------------------------------------