Quartus Prime Pro fatal error
Hi
when we click compile, internal error comes:
Problem Details
Error:
Internal Error: Sub-system: RDB, File: /quartus/db/rdb/rdb_utility.cpp, Line: 1944 rval == nullptr Stack Trace: Quartus 0x100ca4: rdb_find_summary + 0xb4 (db_rdb) Quartus 0x6380d: qcu_update_flow_summary + 0x5d (comp_qcu) Quartus 0xc565a: TILEIP_DS_REPORT::tileip_write_empty_report + 0x2ba (db_tileip) Quartus 0x2c688d: tileip_tileip_init_comb_rpt + 0x1d (db_tileip) Quartus 0x14640: TclInvokeStringCommand + 0xf0 (tcl86) Quartus 0x16442: TclNRRunCallbacks + 0x62 (tcl86) Quartus 0x17c4d: Tcl_EvalEx + 0xa1d (tcl86) Quartus 0xa6a8b: Tcl_FSEvalFileEx + 0x22b (tcl86) Quartus 0xa5136: Tcl_EvalFile + 0x36 (tcl86) Quartus 0x2306c: qexe_evaluate_tcl_script + 0x66c (comp_qexe) Quartus 0x21ba9: qexe_do_tcl + 0x8f9 (comp_qexe) Quartus 0x2a16d: qexe_run_tcl_option + 0x6cd (comp_qexe) Quartus 0x4144f: qcu_run_tcl_option + 0x6ef (comp_qcu) Quartus 0x29929: qexe_run + 0x629 (comp_qexe) Quartus 0x2ab98: qexe_standard_main + 0x268 (comp_qexe) Quartus 0xd8de: qtlg_main + 0x15e (quartus_tlg) 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 0xfb13: __scrt_common_main_seh + 0x10b (quartus_tlg) Quartus 0x2e8d6: BaseThreadInitThunk + 0x16 (KERNEL32) Quartus 0x8c53b: 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: 25.3.0
Build: 109
Edition: Pro Edition
I don't find this IE in the database.
I believe the issue is resolved in Quartus 25.3.1, so I suggest upgrading the design to 25.3.1 in order to fix the problem.
Out of curiosity, does the same issue occur with other devices, e.g., Arria 10?
If yes, could you share the QAR project (Project > Achieve Project) so we could investigate it further?
Regards,
Richard Tan