Forum Discussion

New Contributor

3 years ago

Quartus Prime Pro 22.1 crashes when trying to use Signal Tap Logic Analyzer

Whenever I try to start the Signal Tap Logic Analyzer in a project using the Stratix 10 DX FPGA, Quartus will unconditionally crash with one of the following stack traces. This happens a few seconds after clicking the "Create" button in the template selection dialog while Signal Tap seems to be loading.

Problem Details
Error:

*** Fatal Error: Access Violation at 00007FFAC1FBC6F3
Module: qpro.exe
Stack Trace:
  Quartus          0x1c6f2: ASN_SGATE_HIER_NETLIST_LOADER::create_hieharchy_forest + 0x332 (sld_asn)
  Quartus          0x1dc53: ASN_SGATE_HIER_NETLIST_LOADER::load + 0x53 (sld_asn)
  Quartus          0x2a08a: tbb::internal::function_task<<lambda_85dc533730a8f1b32781bfee97564a95> >::execute + 0x1a (sld_asn)
  Quartus          0x20e8f: tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all + 0x35f (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\custom_scheduler.h:509
  Quartus          0x1da3f: tbb::internal::arena::process + 0x16f (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\arena.cpp:160
  Quartus          0x18ce3: tbb::internal::market::process + 0xe3 (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\market.cpp:693
  Quartus          0x11fbb: tbb::internal::rml::private_worker::run + 0x6b (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\private_server.cpp:270
  Quartus          0x1223a: tbb::internal::rml::private_worker::thread_routine + 0x5a (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\private_server.cpp:223
  Quartus          0x21bb1: _configthreadlocale + 0x91 (ucrtbase)
  Quartus          0x17033: BaseThreadInitThunk + 0x13 (KERNEL32)
  Quartus          0x52650: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Quartus Prime Version 22.1.0 Build 174 03/30/2022 SC Pro Edition

Executable: qpro
Comment:
None

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

Quartus Prime Information
Address bits: 64
Version: 22.1.0
Build: 174
Edition: Pro Edition

Problem Details
Error:

*** Fatal Error: Access Violation at 00007FFAAF1DFBFF
Module: qpro.exe
Stack Trace:
  Quartus           0xfbfe: rml::internal::freeSmallObject + 0x1e (tbbmalloc) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbbmalloc\frontend.cpp:2502
  Quartus          0x14933: std::vector<ASN_SGATE_HIER_NETLIST_LOADER::TREE_NODE * __ptr64,std::allocator<ASN_SGATE_HIER_NETLIST_LOADER::TREE_NODE * __ptr64> >::_Emplace_reallocate<ASN_SGATE_HIER_NETLIST_LOADER::TREE_NODE * __ptr64> + 0x103 (sld_asn)
  Quartus          0x1c705: ASN_SGATE_HIER_NETLIST_LOADER::create_hieharchy_forest + 0x345 (sld_asn)
  Quartus          0x1dc53: ASN_SGATE_HIER_NETLIST_LOADER::load + 0x53 (sld_asn)
  Quartus          0x2a08a: tbb::internal::function_task<<lambda_85dc533730a8f1b32781bfee97564a95> >::execute + 0x1a (sld_asn)
  Quartus          0x20e8f: tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all + 0x35f (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\custom_scheduler.h:509
  Quartus          0x1da3f: tbb::internal::arena::process + 0x16f (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\arena.cpp:160
  Quartus          0x18ce3: tbb::internal::market::process + 0xe3 (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\market.cpp:693
  Quartus          0x11fbb: tbb::internal::rml::private_worker::run + 0x6b (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\private_server.cpp:270
  Quartus          0x1223a: tbb::internal::rml::private_worker::thread_routine + 0x5a (tbb) at quartus\extlibs64\tbb\tbb-2018_U1oss_altera\src\tbb\private_server.cpp:223
  Quartus          0x21bb1: _configthreadlocale + 0x91 (ucrtbase)
  Quartus          0x17033: BaseThreadInitThunk + 0x13 (KERNEL32)
  Quartus          0x52650: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Quartus Prime Version 22.1.0 Build 174 03/30/2022 SC Pro Edition

Executable: qpro
Comment:
None

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

Quartus Prime Information
Address bits: 64
Version: 22.1.0
Build: 174
Edition: Pro Edition

Problem Details
Error:
Internal Error: Sub-system: HDB, File: /quartus/db/hdb/hdb_pdb.cpp, Line: 89
hdb_asgn_to_position == 0
Stack Trace:
  Quartus          0x13551: HDB_ASGN_CONTAINER::customized_pdb_read + 0x79 (DB_HDB)
  Quartus          0x13222: HDB_ASGN_CONTAINER::operator<< + 0x36 (DB_HDB)
  Quartus          0x33684: HDB_SECTION::operator<< + 0x154 (DB_HDB)
  Quartus          0x2d046: HDB_NAMESPACE::operator<< + 0x42 (DB_HDB)
  Quartus           0x73e5: PDB_SEGMENT_READER::finish_reading_all + 0xa5 (DB_PDB)
  Quartus           0x7138: pdb_read_ptr + 0x68 (DB_PDB)
  Quartus         0x135d68: pdb_read<PDB_ARCHIVE,CDB_SGATE_RECONSTRUCT_HDB_INFO> + 0x70 (db_cdb_sgate)
  Quartus         0x1363d1: CDB_SGATE_RECONSTRUCT_HDB_INFO_MODEL_HANDLER::read_model_from_file + 0xf1 (db_cdb_sgate)
  Quartus          0x2d710: QDB_SERVICE_IMPL::get_model_using_handler + 0x350 (db_qdb)
  Quartus          0x2bdd1: QDB_SERVICE_IMPL::get_model + 0x151 (db_qdb)
  Quartus          0x6647c: QDB_BASIC_STATE::load_model_on_demand + 0xcc (db_qdb)
  Quartus          0x669b8: QDB_BASIC_STATE::load_raw_model + 0x88 (db_qdb)
  Quartus          0x660a4: QDB_BASIC_STATE::load + 0xfa4 (db_qdb)
  Quartus         0x14f0ae: QHD_PARTITION_IMPL::load_state + 0x1de (comp_qhd)
  Quartus          0xcfa99: QHD_DATABASE_UTILS::IMPL::load_partition_tree + 0x4c9 (comp_qhd)
  Quartus          0xa7839: QHD_DATABASE_UTILS::load_design + 0x1119 (comp_qhd)
  Quartus           0xd3b7: QHD_DBMUI_MANAGER_IMPL::load_db + 0xe7 (comp_qhd_dbmui)
  Quartus           0xd94e: QHD_DBMUI_MANAGER_IMPL::load_design + 0x22e (comp_qhd_dbmui)
  Quartus           0xfd27: DBMUI_MANAGER::get_qhd_hdb_cmp_action_pt_instance + 0xf7 (DB_DBMUI)
  Quartus          0x58357: SEDQ_TX_MANAGER::check_node_validity + 0xf7 (sld_sedq)
  Quartus          0xf394d: SEDQ_TX_MANAGER::open_document + 0xc5d (sld_sedq)
  Quartus          0xf3c79: SEDQ_FRAME_WND::open_file_from_template + 0xe9 (sld_sedq)
  Quartus          0x6465e: SEDQ_TEMPLATE_DLG::create_new_file + 0x20e (sld_sedq)
  Quartus         0x13c4be: sedq_dyn_template_dlg + 0x2e (sld_sedq)
  Quartus          0xb9296: QUI_TOOLS_MENU::sedq_action + 0x236 (SYS_QUI)
  Quartus         0x1fab9f: QMimeData::urls + 0x13af (Qt5Core)
  Quartus           0x6c76: QAction::activate + 0x136 (Qt5Widgets)
  Quartus         0x160ef7: QMenu::actionGeometry + 0x457 (Qt5Widgets)
  Quartus         0x160d65: QMenu::actionGeometry + 0x2c5 (Qt5Widgets)
  Quartus         0x1663d8: QMenu::mouseReleaseEvent + 0xb8 (Qt5Widgets)
  Quartus          0x39505: QWidget::event + 0x145 (Qt5Widgets)
  Quartus         0x1625bb: QMenu::event + 0x17b (Qt5Widgets)
  Quartus          0x171cc: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)
  Quartus          0x14ed0: QApplication::notify + 0x7d0 (Qt5Widgets)
  Quartus         0x1da788: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core)
  Quartus          0x18531: QApplicationPrivate::sendMouseEvent + 0x331 (Qt5Widgets)
  Quartus          0x613c2: QSizePolicy::QSizePolicy + 0x2792 (Qt5Widgets)
  Quartus          0x5f616: QSizePolicy::QSizePolicy + 0x9e6 (Qt5Widgets)
  Quartus          0x171cc: QApplicationPrivate::notify_helper + 0x13c (Qt5Widgets)
  Quartus          0x1516e: QApplication::notify + 0xa6e (Qt5Widgets)
  Quartus         0x1da788: QCoreApplication::notifyInternal2 + 0xb8 (Qt5Core)
  Quartus          0x5b513: QGuiApplicationPrivate::processMouseEvent + 0x723 (Qt5Gui)
  Quartus          0x46b3a: QWindowSystemInterface::sendWindowSystemEvents + 0x9a (Qt5Gui)
  Quartus         0x227b4d: QEventDispatcherWin32::processEvents + 0xbd (Qt5Core)
  Quartus          0x5a5b8: qt_plugin_query_metadata + 0x1dc8 (qwindows)
  Quartus         0x1d6680: QEventLoop::exec + 0x1a0 (Qt5Core)
  Quartus         0x1d947a: QCoreApplication::exec + 0x14a (Qt5Core)
  Quartus           0x2bee: qgq_main + 0x7e (qpro)
  Quartus          0x1db28: msg_main_thread + 0x18 (CCL_MSG)
  Quartus          0x1e312: msg_thread_wrapper + 0x82 (CCL_MSG)
  Quartus          0x2a313: mem_thread_wrapper + 0x73 (ccl_mem)
  Quartus          0x1b048: msg_exe_main + 0x178 (CCL_MSG)
  Quartus           0x4406: WinMain + 0x156 (qpro)
  Quartus           0x3931: __scrt_common_main_seh + 0x105 (qpro)
  Quartus          0x17033: BaseThreadInitThunk + 0x13 (KERNEL32)
  Quartus          0x52650: 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: 22.1.0
Build: 174
Edition: Pro Edition

11 Replies

RichardT_altera
Super Contributor
3 years ago
Does the Quartus exit with a specific project/design? Will it re-occur if run with different design?
If so, could you help share your project .qar as the engineering team will need it to debug the issue.

Could you try to run the Quartus software as administrator and see if the issue occur?
- yussuf_khalil
  New Contributor
  3 years ago
  Indeed this issue only seems to occur with this specific project. Signal Tap works fine when using an example project generated through Platform Designer. Running Quartus as administrator does not help. I can share the .qar file, however, I'd prefer to do so privately. Can you give me an e-mail address or another means of communication where I can send the file to?
RichardT_altera
Super Contributor
3 years ago
I have drop you an email. Please kindly check your email.
RichardT_altera
Super Contributor
3 years ago
So I just open the .qar project and there is significant long loading time before the Quartus load the project.
Then I can open the Signal Tap GUI and click 'create' without any design compilation.
Is the correct way to duplicate the error? If not, could you help to share the steps?

Best Regards,
Richard Tan
- yussuf_khalil
  New Contributor
  3 years ago
  The long loading times are an issue, too. Is there anything that can be done about that?
  
  I am not sure whether that's important, but I had selected the "mm_ddr4" revision when trying to use Signal Tap. I've also noticed that *sometimes* it works without crashing (I believe about 1 in 5 times) and only crashes again after Quartus was restarted. Perhaps try restarting Quartus a few times if it doesn't occur for you.
RichardT_altera
Super Contributor
3 years ago
I will need consult the engineering team regarding the long loading time.

Please expert that this may takes times depending on the issue complexity.
RichardT_altera
Super Contributor
3 years ago
Just to let you know that we may need some time to work on this.
RichardT_altera
Super Contributor
3 years ago
I think there is something wrong with your .qdb file in your project.
I cant seem to compile the project until I removed the .qdb file and set the preservation level to Not Set in the design partition window. I then able to open the project in a short loading time afterwards.

I tested a few times with the signal tap and it do not crash at all. Unfortunately, I am not able to help you if this is an intermittent issue.
RichardT_altera
Super Contributor
3 years ago
Do you have further question in regards to this case?
RichardT_altera
Super Contributor
3 years ago
I have yet to receive any response from you in regards to my last reply.

With that, I will now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.

Best Regards,
Richard Tan

p/s: If any answer from the community or Intel Support are helpful, please feel free to give best answer or rate 9/10 survey.
yussuf_khalil
New Contributor
3 years ago
Sorry for the late reply. I've found that Signal Tap works fine in Quartus 22.2 (whereas it's still not working properly for me in 22.1), so that issue is probably solved for me. However, can you elaborate on a possible solution for the .qdb file issue? I have seen the long loading times in several different projects. Is it a viable (and safe in terms of data loss) solution to delete the .qdb file and recompile the whole project?

Forum Discussion

Quartus Prime Pro 22.1 crashes when trying to use Signal Tap Logic Analyzer

11 Replies

Recent Discussions

Perpetual license Quartus II doesn't allow to build Cyclone V devices anymore.

Quartus Eda_Writer keeps crashing

Failing IO buffer

Floating point operation on Cyclone 10 GX

Quartus/Signaltap complains about wrong version