Quartus Prime Pro crash-prone

[Seadog]

I keep getting this unwanted message:

I am running QPP 18.1 Build 222 09/21/2018 SJ Pro Edition, on windows 10. The crashes seem to occur most frequently when I am running Timing Analyzer.

Thanks.

[AndyN]

Try doing a Clean Project, then delete the qdb, output_files, and temp-clearbox folders. That usually does the trick...

[Vicky1]

Hi,

"I keep getting this unwanted message:" please provide here the errors/ messages you observed.

In addition, Close the Quartus tool, delete the 'db' & 'incremental_db' folder from project directory then try to recompile & run timing analyzer.

Try to check at your end by creating new fresh project using these files.

Check the Quartus 18.1.2 updates from the 'Updates' tab from link below,

http://fpgasoftware.intel.com/18.1/?edition=pro

Regards,

Vicky

[Vicky1]

Hi,

Have you resolved the issue?

May I know any update?

Regards,

Vicky

[Seadog]

Vicky,

I have not solved the issue. I have tried QPP 19.2, and it also has crashed in a similar manner. In this case, I was cross-probing from Timing Analyzer to Chip Planner (Locate Path-> Locate in Chip Planner).

I can delete the compiler output, but then I do do another build, which can take a couple of hours; so I am disinclined to do that very often.

[Vicky1]

Hi,

"I keep getting this unwanted message:" please provide here the errors/ messages you observed. -------------- if you are able to reproduce please provide that message & screenshot.

'I have not solved the issue. I have tried QPP 19.2, and it also has crashed in a similar manner.' ---- what do you mean crashed ? what you observed exactly?

you can also check by fresh downloading & installing again Quartus prime pro 19.2, it might get corrupted the setup while downloading.

Regards,

Vicky

[Seadog]

Here is a fresh dump from 18.1 Standard:

Problem Details

Error:

*** Fatal Error: Access Violation at 0X00007FF97361C778

Module: quartus.exe

Stack Trace:

0x6c777: ACVQM_OBJECT_INTERFACE::is_underlying_object_valid + 0xe7 (ACE_ACVQ_ACVQM)

0x2d25b: ACVQM_MAPPER::update_given_matrix + 0xcb (ACE_ACVQ_ACVQM)

0x9322f: ACVQM_OBJECT_GROUPING_MANAGER::modify_mapper_with_sets + 0x3ef (ACE_ACVQ_ACVQM)

0x9366e: ACVQM_OBJECT_GROUPING_MANAGER::modify_overlay_set + 0x12e (ACE_ACVQ_ACVQM)

0x8469f: ACVQM_COMMAND_MANAGER::highlight + 0x7f (ACE_ACVQ_ACVQM)

0x4ebbb: acvqc_highlight + 0x9b (ace_acvq_acvqc)

0x161e2: TclNRRunCallbacks + 0x62 (tcl86)

0x17a65: TclEvalEx + 0xa65 (tcl86)

0x18257: Tcl_Eval + 0x37 (tcl86)

0x105e7: atcl_tcl_eval + 0x117 (ccl_atcl)

0x58cbb: ACVQV_LOCATE_HISTORY_VIEW::process_highlight + 0x35b (ACE_ACVQ_ACVQV)

0x517e5: ACVQV_LOCATE_HISTORY_VIEW::qt_static_metacall + 0x165 (ACE_ACVQ_ACVQV)

0x11c420: QMetaObject::activate + 0x520 (QtCore4)

0x160ff9: QAbstractItemModel::dataChanged + 0x39 (QtCore4)

0x4eb2c1: QStandardItemModel::itemChanged + 0x131 (QtGui4)

0x4ed588: QStandardItem::setData + 0x178 (QtGui4)

0x4ed5ea: QStandardItemModel::setData + 0x3a (QtGui4)

0x4f9c73: QStyledItemDelegate::editorEvent + 0x223 (QtGui4)

0x472579: QAbstractItemView::selectionModel + 0x109 (QtGui4)

0x46c0f2: QAbstractItemView::edit + 0xf2 (QtGui4)

0x46fd13: QAbstractItemView::mouseReleaseEvent + 0x183 (QtGui4)

0x4a5d09: QTreeView::mouseReleaseEvent + 0x39 (QtGui4)

0xbd835: AFCQ_TREE_VIEW::mouseReleaseEvent + 0x365 (GCL_AFCQ)

0x60794: QWidget::event + 0xd4 (QtGui4)

0x382676: QFrame::event + 0x36 (QtGui4)

0x47552c: QAbstractItemView::viewportEvent + 0x4ac (QtGui4)

0xc1656: AFCQ_TREE_VIEW::viewportEvent + 0x2b6 (GCL_AFCQ)

0x10f802: QCoreApplicationPrivate::sendThroughObjectEventFilters + 0x82 (QtCore4)

0x22e81: QApplicationPrivate::notify_helper + 0xe1 (QtGui4)

0x21a8e: QApplication::notify + 0x71e (QtGui4)

0x10d92b: QCoreApplication::notifyInternal + 0x7b (QtCore4)

0x25cfe: QApplicationPrivate::sendMouseEvent + 0x1de (QtGui4)

0x856f0: QScrollBar::trUtf8 + 0x1440 (QtGui4)

0x890b1: QApplication::winMouseButtonUp + 0x2761 (QtGui4)

0xca65: DispatchMessageW + 0x6a5 (USER32)

0xc581: DispatchMessageW + 0x1c1 (USER32)

0x132802: QEventDispatcherWin32::processEvents + 0x3e2 (QtCore4)

0x80eb4: QApplicationPrivate::openPopup + 0x204 (QtGui4)

0x10a88b: QEventLoop::exec + 0x22b (QtCore4)

0x10ce6f: QCoreApplication::exec + 0xdf (QtCore4)

0x197b: qgq_main + 0x7b (quartus)

0x12e98: msg_main_thread + 0x18 (CCL_MSG)

0x1467e: msg_thread_wrapper + 0x6e (CCL_MSG)

0x16660: mem_thread_wrapper + 0x70 (ccl_mem)

0x12761: msg_exe_main + 0xa1 (CCL_MSG)

0x24e7: WinMain + 0x127 (quartus)

0x1e58: __tmainCRTStartup + 0x148 (quartus)

0x17973: BaseThreadInitThunk + 0x13 (KERNEL32)

0x6a270: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Executable: quartus

Comment:

None

System Information

Platform: windows64

OS name: Windows 10

OS version: 10.0

Quartus Prime Information

Address bits: 64

Version: 18.1.0

Build: 625

Edition: Standard Edition

[Vicky1]

Hi,

Thanks for the update.

it seems to be a bug but I`m not sure, Could you please provide the project (*.qar)file (Project Menu-> Archive Project...) for replication purpose?

Regards,

Vicky

[Seadog]

I can't post a design to the forum, no.

[Vicky1]

Hello Daniel,

I checked in knowledge database, I couldn`t find the any entry for Quartus crashes by running the timing analyzer.

we(Intel support team) are checking internally so once I got any update I`ll update you.

Thanks for your cooperation & patience.

Regards,

Vicky

[Seadog]

Vicky,

Here is another crash dump, this time from QPP 18.1; this occurred while I was cross-probing from Timing Analyzer to Chip Planner:

Problem Details

Error:

*** Fatal Error: Access Violation at 00007FF984EB0B90

Module: qpro.exe

Stack Trace:

0x70b8f: ACVQM_OBJECT_INTERFACE::is_underlying_object_valid + 0xdf (ACE_ACVQ_ACVQM)

0x2947b: ACVQM_MAPPER::update_given_matrix + 0xcb (ACE_ACVQ_ACVQM)

0x98d11: ACVQM_OBJECT_GROUPING_MANAGER::modify_mapper_with_sets + 0x3f1 (ACE_ACVQ_ACVQM)

0x990fe: ACVQM_OBJECT_GROUPING_MANAGER::modify_overlay_set + 0x12e (ACE_ACVQ_ACVQM)

0x8a2ef: ACVQM_COMMAND_MANAGER::highlight + 0x7f (ACE_ACVQ_ACVQM)

0x3f9db: acvqc_highlight + 0x9b (ace_acvq_acvqc)

0x16442: TclNRRunCallbacks + 0x62 (tcl86)

0x17c4d: TclEvalEx + 0x9ed (tcl86)

0x18437: Tcl_Eval + 0x37 (tcl86)

0x11555: atcl_tcl_eval + 0x125 (ccl_atcl)

0x5a993: ACVQV_LOCATE_HISTORY_VIEW::process_highlight + 0x333 (ACE_ACVQ_ACVQV)

0x55ed2: ACVQV_LOCATE_HISTORY_VIEW::dataChanged + 0x52 (ACE_ACVQ_ACVQV)

0x5b558: ACVQV_LOCATE_HISTORY_VIEW::qt_static_metacall + 0xe8 (ACE_ACVQ_ACVQV)

0x1de156: QMetaObject::activate + 0x576 (Qt5Core)

0x180c8e: QAbstractItemModel::dataChanged + 0x3e (Qt5Core)

0x29c8b8: QStandardItemModel::itemChanged + 0x1d8 (Qt5Gui)

0x29eefb: QStandardItem::setData + 0x31b (Qt5Gui)

0x29ef9a: QStandardItemModel::setData + 0x3a (Qt5Gui)

0x2516fd: QStyledItemDelegate::editorEvent + 0x25d (Qt5Widgets)

0x23897c: QAbstractItemView::selectionModel + 0x19c (Qt5Widgets)

0x231e86: QAbstractItemView::edit + 0xd6 (Qt5Widgets)

0x235f3f: QAbstractItemView::mouseReleaseEvent + 0x16f (Qt5Widgets)

0xb8d04: AFCQ_TREE_VIEW::mouseReleaseEvent + 0x364 (GCL_AFCQ)

0x3a66b: QWidget::event + 0xdb (Qt5Widgets)

0xdb006: QFrame::event + 0x36 (Qt5Widgets)

0x23bfe8: QAbstractItemView::viewportEvent + 0x318 (Qt5Widgets)

0xbc578: AFCQ_TREE_VIEW::viewportEvent + 0x2a8 (GCL_AFCQ)

0x1c0e8c: QCoreApplicationPrivate::sendThroughObjectEventFilters + 0xdc (Qt5Core)

0x18d7b: QApplicationPrivate::notify_helper + 0x12b (Qt5Widgets)

0x1699c: QApplication::notify + 0x8dc (Qt5Widgets)

0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core)

0x1a0d5: QApplicationPrivate::sendMouseEvent + 0x325 (Qt5Widgets)

0x62898: QSizePolicy::QSizePolicy + 0x2d18 (Qt5Widgets)

0x6060d: QSizePolicy::QSizePolicy + 0xa8d (Qt5Widgets)

0x18d8f: QApplicationPrivate::notify_helper + 0x13f (Qt5Widgets)

0x17c16: QApplication::notify + 0x1b56 (Qt5Widgets)

0x1beab8: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core)

0x4cc00: QGuiApplicationPrivate::processMouseEvent + 0x870 (Qt5Gui)

0x345fa: QWindowSystemInterface::sendWindowSystemEvents + 0x9a (Qt5Gui)

0x2084e4: QEventDispatcherWin32::processEvents + 0xd64 (Qt5Core)

0xca65: DispatchMessageW + 0x6a5 (USER32)

0xc581: DispatchMessageW + 0x1c1 (USER32)

0x207cb5: QEventDispatcherWin32::processEvents + 0x535 (Qt5Core)

0x4ff88: qt_plugin_query_metadata + 0x1d18 (qwindows)

0x1ba982: QEventLoop::exec + 0x1b2 (Qt5Core)

0x1bd713: QCoreApplication::exec + 0x143 (Qt5Core)

0x10bb: qgq_main + 0x8b (qpro)

0x13e58: msg_main_thread + 0x18 (CCL_MSG)

0x1516e: msg_thread_wrapper + 0x6e (CCL_MSG)

0x1f900: mem_thread_wrapper + 0x70 (ccl_mem)

0x1348e: msg_exe_main + 0xae (CCL_MSG)

0x20c3: WinMain + 0x153 (qpro)

0x16d2: __scrt_common_main_seh + 0x116 (qpro)

0x17973: BaseThreadInitThunk + 0x13 (KERNEL32)

0x6a270: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Executable: qpro

Comment:

None

System Information

Platform: windows64

OS name: Windows 10

OS version: 10.0

Quartus Prime Information

Address bits: 64

Version: 18.1.0

Build: 222

Edition: Pro Edition

[Vicky1]

Hello,

Thanks for the additional details.

meanwhile you can check the below solution note,

https://www.intel.com/content/altera-www/global/en_us/index/support/support-resources/knowledge-base/tools/2018/fatal-error--access-violation-at-00007ffb48fdbe10.html

Regards,

Vicky

[Seadog]

I have been getting this crash in or when cross-probing to chip planner, but at least lately I have only been running chip planner after doing a complete build (I am generally just pushing the compile button), as I am chasing timing closure. And I have seen the same (or very similar) behavior in QPS 18.1, QPP 18.1, and QPP 19.2. I know Standard and Pro have different compilers, but I suspect the chip planner and perhaps timing analyzer are the same for both tools. It seems most likely a common feature is causing similar problems in both tools.

[JosephC_Intel]

Hi Daniel,

From what being share by Vicky on his last comment on the KDB, do this give you a better picture on how to avoid such crash or error?

We do have same issue reported internally but once we put chip planner as last step during compilation, the standard operation instruction should complete.

Let us know if you still need further support or if we are OK to close this issue for now.

Thanks,

Joseph

[JosephC_Intel]

Hi Daniel,

Can we get some updates here? If further help is required, we can submit this case to engineering.

So, please update us your status.

Thanks,

Joseph