Forum Discussion

BCuze's avatar
BCuze
Icon for New Contributor rankNew Contributor
22 days ago

Q pro 26.1 Netlist Viewer crash

Note : the reporting system seems to still point to Intel...

Quartus Pro 26.1 Crash
Problem Details
Error:
Internal Error: Sub-system: NLWQ, File: /quartus/gcl/nlwq/nlwq_view.cpp, Line: 270
show: bad page number 2
Stack Trace:
Quartus 0x30405e: NLWQ_VIEW::execute_command_line + 0x3e (gcl_nlwq)
Quartus 0x47873: NUIQ_VIEW::change_page + 0xb3 (nlv_nuiq)
Quartus 0xe755: NUIQ_VIEW::qt_static_metacall + 0x285 (nlv_nuiq)
Quartus 0xdfa42: QObject::qt_static_metacall + 0x14c2 (Qt6Core)
Quartus 0xe2463: QMetaObject::activate + 0x83 (Qt6Core)
Quartus 0x20e0: NUIQ_PAGE_TOOLBAR::qt_static_metacall + 0x60 (nlv_nuiq)
Quartus 0xdfa42: QObject::qt_static_metacall + 0x14c2 (Qt6Core)
Quartus 0xe2463: QMetaObject::activate + 0x83 (Qt6Core)
Quartus 0x1383da: QComboBox::editTextChanged + 0x80a (Qt6Widgets)
Quartus 0x1400ca: QComboBox::setCurrentIndex + 0x43a (Qt6Widgets)
Quartus 0x13c2a9: QComboBox::itemIcon + 0x289 (Qt6Widgets)
Quartus 0x13a9d3: QComboBox::iconSize + 0x413 (Qt6Widgets)
Quartus 0xdf9d7: QObject::qt_static_metacall + 0x1457 (Qt6Core)
Quartus 0xe2463: QMetaObject::activate + 0x83 (Qt6Core)
Quartus 0x138ecb: QComboBoxPrivateContainer::eventFilter + 0x50b (Qt6Widgets)
Quartus 0xa4f06: QCoreApplicationPrivate::sendThroughObjectEventFilters + 0xd6 (Qt6Core)
Quartus 0x12f36: QApplicationPrivate::notify_helper + 0x136 (Qt6Widgets)
Quartus 0x110bd: QApplication::notify + 0x6ad (Qt6Widgets)
Quartus 0xa23ce: QCoreApplication::notifyInternal2 + 0x10e (Qt6Core)
Quartus 0x15dd6: QApplicationPrivate::sendMouseEvent + 0x416 (Qt6Widgets)
Quartus 0x7a358: QWidgetRepaintManager::updateStaticContentsSize + 0x2c78 (Qt6Widgets)
Quartus 0x783f0: QWidgetRepaintManager::updateStaticContentsSize + 0xd10 (Qt6Widgets)
Quartus 0x12f51: QApplicationPrivate::notify_helper + 0x151 (Qt6Widgets)
Quartus 0x12100: QApplication::notify + 0x16f0 (Qt6Widgets)
Quartus 0xa23ce: QCoreApplication::notifyInternal2 + 0x10e (Qt6Core)
Quartus 0x97e14: QGuiApplicationPrivate::processMouseEvent + 0x7d4 (Qt6Gui)
Quartus 0xf0fe9: QWindowSystemInterface::sendWindowSystemEvents + 0xe9 (Qt6Gui)
Quartus 0x22941f: QEventDispatcherWin32::processEvents + 0x8f (Qt6Core)
Quartus 0x36fc28: QWindowsGuiEventDispatcher::processEvents + 0x18 (Qt6Gui)
Quartus 0xa8ad3: QEventLoop::exec + 0x1c3 (Qt6Core)
Quartus 0xa07bc: QCoreApplication::exec + 0x15c (Qt6Core)
Quartus 0x2bf7: qgq_py_wrap_main + 0x87 (quartus)
Quartus 0x29568: msg_initialize_out_of_memory_handler + 0x368 (ccl_msg)
Quartus 0x2a772: msg_set_stack_size + 0x92 (ccl_msg)
Quartus 0x2b033: mem_tbb_tracking_flush_peak + 0x773 (ccl_mem)
Quartus 0x2743f: msg_exe_main + 0x17f (ccl_msg)
Quartus 0x42ff: qtEntryPoint + 0x2f (quartus)
Quartus 0x3931: __scrt_common_main_seh + 0x105 (quartus)
Quartus 0x2e956: BaseThreadInitThunk + 0x16 (KERNEL32)
Quartus 0x427b: RtlUserThreadStart + 0x2b (ntdll)
End-trace

Executable: quartus
Comment:
None

System Information
Platform: windows64
OS name: Windows 11
OS version: 10.0.26200

Quartus Prime Information
Address bits: 64
Version: 26.1.0
Build: 110
Edition: Pro Edition

general

3 Replies

  • RichardT_altera's avatar
    RichardT_altera
    Icon for Super Contributor rankSuper Contributor
    22 days ago

    Hi BCuze 

    Could you please share the design .QAR file so we can reproduce the internal error?
    Additionally, could you provide the steps to reproduce the issue?

    Regards,
    Richard Tan

  • BCuze's avatar
    BCuze
    Icon for New Contributor rankNew Contributor
    21 days ago

    Hi Richard,

    Unfortunately, I made many changes in the design and the tech map viewer doesn't display the same thing any more and I don't have the crash now.

    in Timequest :

    • setup summary
    • report timing
    • locate 1st path in tech map viewer
    • select page 2/2 -> crash

    It was reproducible (until I modified the design)

    I have nothing more to offer than the crash report.

    BR

    Bert

    • RichardT_altera's avatar
      RichardT_altera
      Icon for Super Contributor rankSuper Contributor
      21 days ago

      I’m glad to hear the issue has been resolved.
      Unfortunately, for cases involving Fatal or Internal errors, a design test case is required to reproduce the issue. Without being able to replicate it on our side, it is difficult to identify a workaround or solution.
      If you encounter an internal error in the future, please archive the project first before proceeding to made changes in the design. 

      Regards,
      Richard Tan