New Contributor

4 years ago

Signal Tap causing Quartus to crash

I've recently upgraded to Quartus Standard Edition v21.1. I've noticed that when using Signal Tap, if I try to add State machine nodes, this will cause Quartus to crash and generate an error report. I added the report below.

Does anyone know of how to resolve this, or if they're having similar issues?

Problem Details
Error:

*** Fatal Error: Access Violation at 00007FFEACC49E5A

Module: quartus.exe

Stack Trace:

   0x179e59: QDialogButtonBox::button + 0x9 (Qt5Widgets)

    0xe4f8d: SEDQ_STATE_MACHINE_TABLE_VIEW::selectionChanged + 0x5d (sld_sedq)

   0x241036: QAbstractItemView::setSelectionModel + 0x326 (Qt5Widgets)

   0x284cee: QTableView::setSelectionModel + 0x9e (Qt5Widgets)

   0x240c0e: QAbstractItemView::setModel + 0x56e (Qt5Widgets)

   0x284224: QTableView::setModel + 0x204 (Qt5Widgets)

    0x1a10f: SEDQ_STATE_MACHINE_TABLE_VIEW::SEDQ_STATE_MACHINE_TABLE_VIEW + 0x15f (sld_sedq)

    0x9f195: SEDQ_STATE_MACHINE_DLG::on_init_dlg + 0x345 (sld_sedq)

    0x19f1c: SEDQ_STATE_MACHINE_DLG::SEDQ_STATE_MACHINE_DLG + 0xac (sld_sedq)

    0xa7c6d: SEDQ_VIEW::on_node_add_state_machine + 0x4d (sld_sedq)

   0x1fa79f: QMimeData::urls + 0x13af (Qt5Core)

     0x7116: QAction::activate + 0x136 (Qt5Widgets)

   0x161ee7: QMenu::actionGeometry + 0x457 (Qt5Widgets)

   0x161d55: QMenu::actionGeometry + 0x2c5 (Qt5Widgets)

   0x167348: QMenu::mouseReleaseEvent + 0xb8 (Qt5Widgets)

    0x3a0a5: QWidget::event + 0x145 (Qt5Widgets)

   0x1635bb: QMenu::event + 0x17b (Qt5Widgets)

    0x179ec: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)

    0x156f0: QApplication::notify + 0x7d0 (Qt5Widgets)

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

    0x18d51: QApplicationPrivate::sendMouseEvent + 0x331 (Qt5Widgets)

    0x62022: QSizePolicy::QSizePolicy + 0x2792 (Qt5Widgets)

    0x60276: QSizePolicy::QSizePolicy + 0x9e6 (Qt5Widgets)

    0x179ec: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)

    0x1598e: QApplication::notify + 0xa6e (Qt5Widgets)

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

    0x5b733: QGuiApplicationPrivate::processMouseEvent + 0x723 (Qt5Gui)

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

   0x2273bd: QEventDispatcherWin32::processEvents + 0xbd (Qt5Core)

    0x59b48: qt_plugin_query_metadata + 0x1db8 (qwindows)

   0x1d63b0: QEventLoop::exec + 0x1a0 (Qt5Core)

   0x163af7: QMenu::exec + 0x1c7 (Qt5Widgets)

   0x1638ea: QMenu::exec + 0x1a (Qt5Widgets)

    0x3cff3: SEDQ_VIEW::contextMenuEvent + 0x173 (sld_sedq)

    0x3a694: QWidget::event + 0x734 (Qt5Widgets)

    0x58797: SEDQ_VIEW::event + 0x47 (sld_sedq)

    0x179ec: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)

    0x15f26: QApplication::notify + 0x1006 (Qt5Widgets)

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

    0x6286e: QSizePolicy::QSizePolicy + 0x2fde (Qt5Widgets)

    0x60276: QSizePolicy::QSizePolicy + 0x9e6 (Qt5Widgets)

    0x179ec: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)

    0x1598e: QApplication::notify + 0xa6e (Qt5Widgets)

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

    0x5b733: QGuiApplicationPrivate::processMouseEvent + 0x723 (Qt5Gui)

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

   0x2273bd: QEventDispatcherWin32::processEvents + 0xbd (Qt5Core)

    0x59b48: qt_plugin_query_metadata + 0x1db8 (qwindows)

   0x1d63b0: QEventLoop::exec + 0x1a0 (Qt5Core)

   0x1d924a: QCoreApplication::exec + 0x14a (Qt5Core)

     0x10bb: qgq_main + 0x8b (quartus)

    0x13638: msg_main_thread + 0x18 (CCL_MSG)

    0x1494e: msg_thread_wrapper + 0x6e (CCL_MSG)

    0x18520: mem_thread_wrapper + 0x70 (ccl_mem)

    0x12df1: msg_exe_main + 0xa1 (CCL_MSG)

     0x20c6: WinMain + 0x156 (quartus)

     0x16d2: __scrt_common_main_seh + 0x116 (quartus)

    0x17c23: BaseThreadInitThunk + 0x13 (KERNEL32)

    0x6d720: RtlUserThreadStart + 0x20 (ntdll)

End-trace



Executable: quartus
Comment:
I tried to add state machine nodes in Signal Tap which caused Quartus to crash

System Information
Platform: windows64
OS name: Windows 10
OS version: 10.0

Quartus Prime Information
Address bits: 64
Version: 21.1.0
Build: 842
Edition: Standard Edition

20 Replies

SyafieqS
Super Contributor
4 years ago
Nigel,

Is it possible for you to shared the design or small design that able to reproduce this issue? I will check this at my end.
Also, step to reproduce it, you can share via email if it is confidential.
SyafieqS
Super Contributor
4 years ago
Nigel,

May I know if there is any update regarding my request
This would be a bug for new Quartus engine with state machine node and stp.
Thus need design to be replicated.
- NJackson
  New Contributor
  3 years ago
  Hi,
  
  I’ve attached the project that I discovered the issue in (it effects other projects as well so appears to be a general v21.1 issue)
  OEM_Prototype.zip1.3 MB
SyafieqS
Super Contributor
3 years ago
Nigel,

Thank you.
Let me reproduce this let you know any update.
SyafieqS
Super Contributor
3 years ago
Hi Nigel,

Once I unzip and try to compile, I encountered such issue as below.

I am not able to reproduce this, therefore need your design with no error as below.
SyafieqS
Super Contributor
3 years ago
You can attached it here as well the zip/qar
SyafieqS
Super Contributor
3 years ago
Hi Nigel,

May I know if there is any update from my previous reply?
I encountered and error related to quartus locating a script tcl file during unarchiving.
Can you reattach the design with previous issue solved?
- NJackson
  New Contributor
  3 years ago
  Hi,
  
  I've reattached with design with the reference to the tcl file at compile time removed.
  
  This should now compile for you.
  OEM_Prototype.zip749 KB
SyafieqS
Super Contributor
3 years ago
Nigel,

Thank you.
Let me reproduce this and let you know any update.
AEvers
New Contributor
3 years ago
I observed the same issue with different designs (signal tap was running with these designs in Quartus 20.1 without any issue). Is there any solution for this topic?
SyafieqS
Super Contributor
3 years ago
Hi Nigel,

I cant reproduce the issue mentioned related to internal error with recent attached design. I was able to compile it successfully without issue.
Can we have a quick call to discuss more on this if that's possible?
SyafieqS
Super Contributor
3 years ago
I was testing on Linux, let me check whether Win 10 can reproduce this.