Internal Error: Sub-system: TDC, File: /quartus/tsm/tdc/tdc_accessories_delay_budget.

[Altera_Forum]

Anyone found a way to avoid hitting this internal error? 

I've been hitting it more & more frequently, and can't seem to avoid it any longer. Since it takes ~45 mins for the build to get to the point where it hits this (& dies), it's eating a lot of my time.     Internal Error: Sub-system: TDC, File: /quartus/tsm/tdc/tdc_accessories_delay_budget.cpp, Line: 1991 edge_delay_data[edge_id].reference_ic_delay >= ic_delay - 10 Stack Trace: 0x14acd: TDC_ACCESSORIES_DELAY_BUDGET::use_saved_min_delay_budget_calculation_starting_points_to_update_ic_delays + 0x14d (TSM_TDC) 0x11c31: TDC_ACCESSORIES_DELAY_BUDGET::perform_slack_allocation + 0xdc1 (TSM_TDC) 0x28abe: TDC_COMMON_ACCESSORIES::perform_slack_allocation + 0x4e (TSM_TDC) 0x2a79d9: _Dinkum_std::map<int,TDB_NODE *,_Dinkum_std::less<int>,MEM_STL_ALLOCATOR<_Dinkum_std::pair<int,TDB_NODE *> > >::~map<int,TDB_NODE *,_Dinkum_std::less<int>,MEM_STL_ALLOCATOR<_Dinkum_std::pair<int,TDB_NODE *> > > + 0x339 (fitter_vpr20kmain) 0x2a328c: _vpr_qi_timing_direct_api_get_delay_budget_data + 0x25c (fitter_vpr20kmain) 0x204fbd: _altera_timing_calculate_delay_budget_data + 0x19d (fitter_vpr20kmain) 0x1e9ab9: _aa_rt_perform_route_processing_after_first_iteration + 0x439 (fitter_vpr20kmain) 0x7d7c: mem_delete_helper + 0x9c (ccl_mem) 0x197589: _aa_route_alg_get_iteration_stats + 0x1d39 (fitter_vpr20kmain) 0x1968b4: _aa_route_alg_get_iteration_stats + 0x1064 (fitter_vpr20kmain) 0x195ca5: _aa_route_alg_get_iteration_stats + 0x455 (fitter_vpr20kmain) 0x1945a7: _aa_route_alg_perform_timing_driven_route + 0x47 (fitter_vpr20kmain) 0x1a7e8b: _aa_route_try_route + 0x11b (fitter_vpr20kmain) 0x13713c: _aa_flow_get_fit_attempt_string + 0xf1c (fitter_vpr20kmain) 0x136d21: _aa_flow_get_fit_attempt_string + 0xb01 (fitter_vpr20kmain) 0x135dda: _aa_flow_fit + 0xca (fitter_vpr20kmain) 0x8b8a9: _vpr_main_internal + 0x399 (fitter_vpr20kmain) 0x2672ae: VPR_QI_FACADE::vpr_qi_main + 0x12e (fitter_vpr20kmain) 0x2a552: _fitapi_run_vpr + 0x72 (fitter_fitapi) 0x3763d: FITCC_EXPERT::run_vpr + 0x11d (FITTER_FITCC) 0x388dc: FITCC_EXPERT::place_and_route + 0x13c (FITTER_FITCC) 0x39ae8: FITCC_EXPERT::invoke_fitter + 0x6a8 (FITTER_FITCC) 0x245a: _ftitan_execute + 0x22a (fitter_ftitan) 0x9940: fmain_start + 0x710 (FITTER_FMAIN) 0x741c: qfit_execute_fit + 0x19c (quartus_fit) 0x11a95: QFIT_FRAMEWORK::execute + 0x4b5 (quartus_fit) 0xd9e1: qexe_get_tcl_sub_option + 0x981 (comp_qexe) 0x10287: qexe_process_cmdline_arguments + 0x387 (comp_qexe) 0x10374: qexe_standard_main + 0x84 (comp_qexe) 0xb79e: qfit_main + 0x5e (quartus_fit) 0x1ce1: msg_main_thread + 0x11 (CCL_MSG) 0x1bc8: _thr_final_wrapper + 0x8 (ccl_thr) 0x1c55: msg_thread_wrapper + 0x85 (CCL_MSG) 0x6720: mem_thread_wrapper + 0x32 (ccl_mem) 0x2c423: msg_exe_main + 0x63 (CCL_MSG) 0xbc3c: _main + 0x1c (quartus_fit) 0x13afb: _memset + 0x15f (quartus_fit) 0x17076: RegisterWaitForInputIdle + 0x48 (kernel32)   End-trace   Quartus II Version 10.1 Build 153 11/29/2010 SJ Full Version

[Altera_Forum]

--- Quote Start ---  Anyone found a way to avoid hitting this internal error? I've been hitting it more & more frequently, and can't seem to avoid it any longer. Since it takes ~45 mins for the build to get to the point where it hits this (& dies), it's eating a lot of my time.    --- Quote End ---    Hi Briane,  I'm sorry that you're hitting this error - I'm part of the team that owns this code. Can you please submit an SR that includes a QAR of your design at https://www.altera.com/myaltera?  Cheers, Adrian

[Altera_Forum]

Hi Adrian, thanks for the quick reply. It's SR# 10795756, and has a full 'service request w/ incremental database' qar attached so it will hopefully be easy for you to reproduce. Thanks & good luck. I'll keep my fingers crossed for a workaround. ;) -Brian

[Altera_Forum]

--- Quote Start ---  Hi Adrian, thanks for the quick reply. It's SR# 10795756, and has a full 'service request w/ incremental database' qar attached so it will hopefully be easy for you to reproduce. Thanks & good luck. I'll keep my fingers crossed for a workaround. ;) -Brian  --- Quote End ---    Hi Brian, we couldn't reproduce this on a 64-bit Windows build. What OS and build (32 or 64 bit) were you using?

[Altera_Forum]

Hi, it's Windows XP Pro SP3 (32b), w/ an Intel X9770@3.2GHz w/ 4GB of RAM.

[Altera_Forum]

Also, note that this is compiled without a megacore ip license for the rapidio (in case that affects the generated IP timeout logic & affects your reproducibility).