Windows 10 with 25GB available RAM and plenty of swap space.
My design is SIGNIFICANTLY smaller than the 10K executable code line limit for the Intel-FPGA ModelSim Starter edition unless some ALTCLKCTRL and ALTPLL IP modules involve 1000s of "executable lines".
My individual modules and even small subsets of modules work fine but when I go over some magic number the ModelSim simulator crashes after many 100s (718 to be exact) of Memory allocation failure messages.
The messages are of the form:
# ** Fatal: (vsim-4) ****** Memory allocation failure. *****
# Attempting to allocate XXXXXX bytes
# Please check your system for available memory and swap space.
where "XXXXXX" are values between 131072 and 1040. The number of bytes requested in the allocations requests don't really follow any easilt discernible pattern ... some are powers of 2 and others are not also.
In the end I get a different message:
# ** Fatal: (SIGSEGV) Bad handle or reference.
# Time: 0 ps Iteration: 0 Process:
There is no message saying I have exceeded the executable line limit.
There is no popup indicating an error.
I found the error messages in the transcript file.
Does anyone have any idea what I am doing wrong ... or how I can work around this issue?
Hi @RIvy ,
Let me know if this has helped resolve the issue you are facing or if you need any further assistance.
Thank you for the response.
Looks like the issue is with the WLF simulation file being in use by another user/program. This is the warning from ModelSim before it crashes trying to allocate more memory.
# ** Warning: (vsim-WLF-5000) WLF file currently in use: vsim.wlf
# File in use by: Richa Hostname: ECS-ZBOOK-17-G4 ProcessID: 50584
# Attempting to use alternate WLF file "./wlftykv95n".
# ** Warning: (vsim-WLF-5001) Could not open WLF file: vsim.wlf
# Using alternate file: ./wlftykv95n
I suggest you check if any other modelsim processes are in use via the Task Manager and kill it. Close all Quartus/ModelSim tools and kill all vsim/vlog processes that are running via Task Manager. Then re-open the project and try running the simulation.