Quartus Pro 25.3 crash using rhel7/8 - Quartus Pro 25.3 crash using rhel7/8 Hello everybody I'm working on an Agilex-5 project since fex months on our internal couputer farm using Quartus Pro 25.3. To generate the final bitstream, a bash script is used to execute all the steps. Until now, we have no specific issue using this script with Quartus. But since few days, we're unable to generate the project because Quartus Pro returns strange errors (see attachments). We also tried to use latest 23.5.1 version on an Ubuntu host under WSL and we also saw the same errors. Running Quartus GUI may also end with same error. (see quartus_4.png) Has anyone already experienced this issue? Thanks a lot Benjamin Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Yes, it looks the patch helps. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Yes, it looks the patch helps. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Hi, it's stated very clearly that all Quartus Pro versions >= 23.3 up to recent 25.3.1 need the patch. You can install it for all used versions without wasting time by checking if the error occurs on your PC. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Yes, that is the same problem. You must install the patch mentioned in the KDB article linked above, it should be 1.31 for Quartus 25.1.1. Not sure what patch 1.03 is but you can have both. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 We are seeing a very similar issue on Windows with Quartus Prime Pro 25.1.1 Build 125 + Patch 1.03. Compilation (Analysis & Synthesis) freezes reproducibly depending on the system time: Before ~11 AM: compilation always completes normally. After ~11 AM: the first compilation attempt of the day hangs indefinitely. This happens even: – immediately after reboot, – on weekends, – with all db/, qdb/, and temp folders deleted, – using both GUI and quartus_sh --flow compile, – with Platform Designer closed or open. We confirmed that if we manually set the system clock back to the morning (e.g., 08:00), the same project compiles successfully again. If we restore the real time → the freeze returns. This looks very similar to the recent reports of unexpected freezes in various Quartus 24.x–25.x versions starting around mid‑January 2026. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 You can get the patch from this KDB: https://community.altera.com/kb/knowledge-base/why-do-i-unexpectedly-observe-intermittent-ddm-errors/349714 Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Hi, Thanks a lot for the link, it works for me (25.3.1 linux) Best regards, Benjamin Replies: Re: Quartus Pro 25.3 crash using rhel7/8 All errors of this kind, starting to appear on Jan 10, are solved and patches are available at Why do I unexpectedly observe intermittent DDM Errors? | Altera Community Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Hi all, The KDB link had been live check https://community.altera.com/kb/knowledge-base/why-do-i-unexpectedly-observe-intermittent-ddm-errors/349714 Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Hi, Can you confirm that patches for Quartus Prime Pro v25.3.0.109 will be available ? It's the latest version with Stratix10, Arria10 and Cyclone10 device support (v25.3.1.100 only support AgileX variants). Cheers, Steffen Replies: Re: Quartus Pro 25.3 crash using rhel7/8 We experience the same error since January 10, 2026: Error (22912): Unhandled exception: Fatal Error: Assertion failed tools/cpp/ddm/ddm_assessor.cpp:53: DDM_T::verify_token(token) : Cannot identify the client from function assertion_error in tools/cpp/ddm_report/ddm_report_msg.cpp@455 Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Could we get an estimate when the patch will be available? Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Thank you, ShengN_altera . Can you please provide an estimated time frame for the patch? Thanks, -Roee Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Hi, We are also seeing a similar issue. Error (22912): Unhandled exception: Fatal Error: Assertion failed tools/cpp/ddm/ddm_assessor.cpp:53: DDM_T::verify_token(token) : Cannot identify the client from function assertion_error in tools/cpp/ddm_report/ddm_report_msg.cpp@455 We use Quartus 24.2, and the problem seemed to appear on Saturday 10th of January 2026. Sometimes the compilations get stuck at the synthesis stage, sometimes it works after retrying. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Has anyone tested this by setting the PC date to before January 10, 2026? I just tested this, and as expected it does not work. Quartus/flexlm detects date set back. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Hi Thanks a lot to you and everybody for feedbacks. Have a great day. Best regards, Benjamin Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Hi, Internal message as below: There was a Quartus Prime Pro issue broadly discovered by customers, field and internal teams in which the Quartus code that calculates the date and time from the DDM client ID mistakenly identifies the time being shifted an hour from the current time which in turn, causes a Quartus crash to take place. This issue began when the year turned to 2026 and we moved to a two-digit date in the month of January. This crash affects: Quartus Prime Pro Software versions v23.3 through v25.3.1 Quartus Embedded Edition v25.3 and v25.3.1 Quartus Programmer v23.3 through v25.3.1 This issue can be seen when using Quartus software through command line or GUI interface. Quartus Patch requests have been filed for the above software and tools. A KDB draft is available and will be reviewed and released when the patches are ready. These fixes and KDB are being driven with utmost priority. Will get back once the patch and kdb are available. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 We confirm that we are experiencing the same crash issue with Quartus Pro 24.3 and 24.1 across multiple servers, all running Ubuntu 24.04. The issue began on the morning of January 10, 2026. We have verified that all licenses are valid; however, compilation consistently crashes with an unknown internal error. The same setup worked previously without any issues. Replies: Re: Quartus Pro 25.3 crash using rhel7/8 I too am seeing similar issues that seem to have cropped up out of nowhere in the past 48 hours. Intermittent crashes of Quartus Pro (running in shell mode) occurring seemingly at random at varying stages of the flow, and also intermittent failures immediately upon launch of Quartus Pro (in shell mode) resulting in an identical error message and stack trace to those shown in the original poster's screen shot quartus_4.PNG. I'm seeing this occur with multiple versions of Quartus Pro (24.2, 25.1, 25.3.1) running on several different machines and different operating systems (RHEL 8 and RHEL 9), all of which were working perfectly up until the past couple of days. -Roee Replies: Re: Quartus Pro 25.3 crash using rhel7/8 I can confirm that I’m experiencing the same errors when running Quartus Pro 25.3 in Docker containers. Since Sunday (11/01/2026), none of my Quartus Pro 23.3 GUI installations have been working on either Windows 11 or Ubuntu 24.04. All of them hang when attempting to perform place-and-route (P&R) on a design. The same source code, scripts, and settings were working on Windows 11, Ubuntu 24.04, and Docker PCs on Saturday (10/01). I’m currently unable to perform P&R on any Quartus Pro design. If anyone has a workaround for this issue, please share it here Replies: Re: Quartus Pro 25.3 crash using rhel7/8 Hi, We have also started seeing similar errors today. We have two PCs running Ubuntu 22.04.5 LTS (GNU/Linux 6.8.0-90-generic x86_64) and Quartus 24.1. It does not crash consistently each time. Below are some of the errors: Starting Quartus: $ /opt/tools/altera/intelFPGA_pro/24.1/quartus/bin/quartus & Error (22912): Unhandled exception: Fatal Error: Assertion failed tools/cpp/ddm/ddm_assessor.cpp:53: DDM_T::verify_token(token) : Cannot identify the client from function assertion_error in tools/cpp/ddm_report/ddm_report_msg.cpp@455 *** Fatal Error: Program termination requested *** *** Below is the stack trace at the time the error occurred. *** The lines beginning "Err Handler" represent frames relating *** to generating this report. *** The point at which the error occurred is somewhere after these lines. *** There may be a few frames representing standard/library code *** before the Quartus frames begin. *** The search for the error should begin with the Quartus frames. *** Unwinder: libunwind *** Stack depth: 15 Quartus 0x22142: err_terminator() + 0x1a4 (ccl_err) Quartus 0xa916a: __cxxabiv1::__terminate(void (*)()) + 0xa (stdc++) Quartus 0xa91d5: (stdc++) Quartus 0xa9428: (stdc++) Quartus 0x154eb: void ddm_throw<DDM_RUNTIME_ERROR>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x3bb (ddm_report) Quartus 0x12cf9: DDM_REPORT::DDM_ASSERTION_HANDLER::assertion_error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) const + 0xc9 (ddm_report) Quartus 0x11918: DDM_REPORT::ASSERTION_HANDLER::error(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x68 (ddm_report) Quartus 0x12bd6: DDM_REPORT::detail::assert_at_line(char const*, char const*, int, char const*, ...) + 0x1b6 (ddm_report) Quartus 0x1ad479: ddm_set_lassessor(DDM_T_ASSESSOR*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x49 (ddm) Quartus 0xd2294: DMS_MANAGER::DMS_MANAGER() + 0x456 (dni_dms) Quartus 0xd23c4: DMS_MANAGER::get() + 0x7a (dni_dms) Quartus 0xd45be: _GLOBAL__sub_I_dms_manager.cpp + 0x7d (dni_dms) Quartus 0x647e: (ld-linux-x86-64) Quartus 0x6568: (ld-linux-x86-64) Quartus 0x202ca: (ld-linux-x86-64) During compilation: Error: UNAVAILABLE: Network closed for unknown reason Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNAVAILABLE: io exception Error: finishConnect(..) failed: Connection refused: localhost/127.0.0.1:35607 Error: UNKNOWN: Application error processing RPC Error: UNKNOWN: Application error processing RPC Error: UNKNOWN: Application error processing RPC Error: UNKNOWN: Application error processing RPC Error: UNKNOWN: Application error processing RPC Error: Quartus Prime IP Generation Tool was unsuccessful. 132 errors, 22 warnings Error: Peak virtual memory: 992 megabytes Error: Processing ended: Mon Jan 12 17:55:06 2026 Error: Elapsed time: 00:00:52 Error: System process ID: 1339331 Error(21794): Quartus Prime Full Compilation was unsuccessful. 134 errors, 22 warnings serv_req_info.txt: <?xml version="1.0" encoding="utf-8"?> <internal_error> <sub_system>ERR</sub_system> <callstack>*** Fatal Error: 0x7f9e34172142: ccl_err + 0x22142 (_Z14err_terminatorv + 0x1a4) 0x7f9e2faa916a: stdc++ + 0xa916a (_ZN10__cxxabiv111__terminateEPFvvE + 0xa) 0x7f9e2faa91d5: stdc++ + 0xa91d5 0x7f9e2faa9428: stdc++ + 0xa9428 0x7f9e2f0924eb: ddm_report + 0x154eb (_Z9ddm_throwI17DDM_RUNTIME_ERROREvRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE + 0x3bb) 0x7f9e2f08fcf9: ddm_report + 0x12cf9 (_ZNK10DDM_REPORT21DDM_ASSERTION_HANDLER15assertion_errorENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE + 0xc9) 0x7f9e2f08e918: ddm_report + 0x11918 (_ZN10DDM_REPORT17ASSERTION_HANDLER5errorENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE + 0x68) 0x7f9e2f08fbd6: ddm_report + 0x12bd6 (_ZN10DDM_REPORT6detail14assert_at_lineEPKcS2_iS2_z + 0x1b6) 0x7f9e1edad479: ddm + 0x1ad479 (_Z17ddm_set_lassessorP14DDM_T_ASSESSORRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE + 0x49) 0x7f9e30545294: dni_dms + 0xd2294 (_ZN11DMS_MANAGERC1Ev + 0x456) 0x7f9e305453c4: dni_dms + 0xd23c4 (_ZN11DMS_MANAGER3getEv + 0x7a) 0x7f9e305475be: dni_dms + 0xd45be (_GLOBAL__sub_I_dms_manager.cpp + 0x7d) 0x7f9e35c9147e: ld-linux-x86-64 + 0x647e 0x7f9e35c91568: ld-linux-x86-64 + 0x6568 0x7f9e35cab2ca: ld-linux-x86-64 + 0x202ca </callstack> <error>Program termination requested</error> <date>Mon Jan 12 17:54:02 2026 </date> <version>Version 24.1.0 Build 115 03/21/2024 SC Pro Edition</version> </internal_error> Replies: Re: Quartus Pro 25.3 crash using rhel7/8 I forgot to mention that we're using LSF8 for dispatching jobs on the computer farm.