Quartus disregards allocated RAM specification and num_processors ?

Hello,

I also use a Cyclone V (using Quartus Prime Version 22.1std.1 Build 917 02/14/2023 SC Standard Edition) under red hat 7,

I see this in the output_files/*.flow.rpt:

; Flow Elapsed Time                                                                                                        ;
+----------------------+--------------+-------------------------+---------------------+------------------------------------+
; Module Name          ; Elapsed Time ; Average Processors Used ; Peak Virtual Memory ; Total CPU Time (on all processors) ;
+----------------------+--------------+-------------------------+---------------------+------------------------------------+
; Analysis & Synthesis ; 00:07:18     ; 2.0                     ; 2780 MB             ; 00:10:16                           ;
; Total                ; 00:07:18     ; --                      ; --                  ; 00:10:16                           ;
+----------------------+--------------+-------------------------+---------------------+------------------------------------+

And as for the lsf jobs report, I see this:

------------------------------------------------------------
# LSBATCH: User input
quartus_map wld_fpga_top
------------------------------------------------------------

Successfully completed.

Resource usage summary:

    CPU time :                                   672.50 sec.
    Max Memory :                                 4694 MB
    Average Memory :                             1754.22 MB
    Total Requested Memory :                     3000.00 MB
    Delta Memory :                               -1694.00 MB
    Max Swap :                                   -
    Max Processes :                              9
    Max Threads :                                27
    Run time :                                   501 sec.
    Turnaround time :                            511 sec.

(I use in the .qsf set_global_assignment -name NUM_PARALLEL_PROCESSORS 6 )

I think the mapping phase is mostly using one or 2 CPU cores but It can use more during fitting phase (I will post it when I get the result).

As for the crash, I guess Quartus is stuck in a loop with your design, try to remove any timing constraint in the .sdc to see if this is not related to one of them.