Quartus Crashes when Exporting Design Partition

[SFost3]

When trying to export a .qdb file in Quartus 23.3 and up the program crashes, below is the log.

I've been able to do this successfully on previous versions and upgrading to 24.2 didn't help either. 

I've tried cleaning the project and deleting all non-source files among other things and nothing has helped. I've tried on a Windows 10 machine and a different Windows 11 machine. Both have the same issue.

Assistance would be appreciated.

Problem Details
Error:

*** Fatal Error: Access Violation at 00007FF89FA1B01A
Module: quartus_cdb.exe
Stack Trace:
Quartus 0xbb019: CDB_ATOM_ITERM::get_source + 0x9 (db_cdb_atom)
Quartus 0x12ceb1: QHD_EXPORT_IMPORT::get_any_bb_iterms_driven_by_common_src + 0x3c1 (comp_qhd)
Quartus 0x12917f: QHD_EXPORT_IMPORT::export_block_checks + 0xdbf (comp_qhd)
Quartus 0x127b64: QHD_EXPORT_IMPORT::export_block + 0x744 (comp_qhd)
Quartus 0x4d187: DSGN_FACADE::export_block + 0x10d7 (sys_dsgn)
Quartus 0x26456: dsgn_export_block + 0x656 (sys_dsgn)
Quartus 0x16442: TclNRRunCallbacks + 0x62 (tcl86)
Quartus 0x17c4d: TclEvalEx + 0x9ed (tcl86)
Quartus 0xa6a8b: Tcl_FSEvalFileEx + 0x22b (tcl86)
Quartus 0xa5136: Tcl_EvalFile + 0x36 (tcl86)
Quartus 0x22460: qexe_evaluate_tcl_script + 0x640 (comp_qexe)
Quartus 0x21062: qexe_do_tcl + 0x8c2 (comp_qexe)
Quartus 0x29837: qexe_run + 0x507 (comp_qexe)
Quartus 0x2ac84: qexe_standard_main + 0x264 (comp_qexe)
Quartus 0x150fc: qatm_main + 0x6c (quartus_cdb)
Quartus 0x27f08: msg_main_thread + 0x18 (ccl_msg)
Quartus 0x28ec2: msg_thread_wrapper + 0x82 (ccl_msg)
Quartus 0x2c323: mem_thread_wrapper + 0x73 (ccl_mem)
Quartus 0x25b65: msg_exe_main + 0x175 (ccl_msg)
Quartus 0x1966f: __scrt_common_main_seh + 0x10b (quartus_cdb)
Quartus 0x17373: BaseThreadInitThunk + 0x13 (KERNEL32)
Quartus 0x4cc90: RtlUserThreadStart + 0x20 (ntdll)

End-trace

Executable: quartus
Comment:
None

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

Quartus Prime Information
Address bits: 64
Version: 23.3.0
Build: 104
Edition: Pro Edition

[ShengN_Intel]

Hi,

Possible to provide the design file for testing out. You may provide the design privately to me as well.

Thanks,

Regards,

Sheng

[SFost3]

What design file specifically? I can't provide the entire design but maybe I can try making a small project with the same problem.

I also discovered that if I completely compile the project I am able to successfully export the final snapshot but exporting the synthesized snapshot still causes a crash.

[ShengN_Intel]

Hi,

Sure. Let me know if the small project available with you.

Thanks,

Regards,

Sheng

[SFost3]

Hi, 

 I managed to reproduce the problem in a small project. How can I share it with you privately?

Regards

[ShengN_Intel]

Hi,

You may share to my working email address qi.sheng.ng@intel.com

[ShengN_Intel]

Hi,

I had reported the problem and will get back to you once there's any further feedback.

Thanks,

Regards,

Sheng

[SFost3]

Hi Sheng,

Is there an update on this yet?

Thanks

[ShengN_Intel]

Hi,

I had notified again the engineering team. Will get back to you once any further feedback.

Thanks,

Regards,

Sheng

[ShengN_Intel]

Hi,

The fix is planned in 24.3.

POSSIBLE WORKAROUNDS from engineering team:

1. Modify the RTL to split the BIDIRs into separate inputs/outputs so that we don't get a buffer in the nested partition.
2. Remove the PARTITION assignment if the design is usable in its entirety.

Let me know if the workarounds help.

Thanks,

Regards,

Sheng

[ShengN_Intel]

Hi,

Let me know if the workaround resolves the problem from your side.

Thanks,

Regards,

Sheng

[SFost3]

Hi Sheng,

Sorry for the delay, I was on vacation.

Thanks for having this looked at and glad to hear there's a solution/update.
I'll give it a try when I have the chance and I'll let you know if it helps.

Regards

[ShengN_Intel]

Hi,

Sure. Let me know if the workaround helps.

Thanks,

Regards,

Sheng

[ShengN_Intel]

Hi,

Does your problem being resolved with the workaround?

Thanks,

Regards,

Sheng

[SFost3]

Hi Sheng,

The workaround appears to be working thanks.

Regards,
Samuel