Forum
Important Notice for New User Registrations
To combat an increasing number of spam and bot registrations, we now manually approve all new user registrations. While this may cause a delay until your account is approved, this step is essential to ensure the quality and security of this forum.
To help us verify your registration as legitimate, please use a clear name as user name or an official email address (such as a work, university, or similar address). If you’re concerned that we may not recognize your registration as non-spam, feel free to email us at with a request to approve your username.
Question about running large simulation file
Quote from Chris on 13. March 2025, 00:58Dear David,
I have tried a few times to run Free-vortex wake method with storing replay and sensor output on Linux system, and I have paused and save the files in some certain period to ensure have some backup of the file. I noticed when the QBlade file is above 100GB, the simulation will be easily “killed” and I checked there is no warning in the log console but just show “killed”. Do you have any idea about this error?
thanks
Chris
Dear David,
I have tried a few times to run Free-vortex wake method with storing replay and sensor output on Linux system, and I have paused and save the files in some certain period to ensure have some backup of the file. I noticed when the QBlade file is above 100GB, the simulation will be easily “killed” and I checked there is no warning in the log console but just show “killed”. Do you have any idea about this error?
thanks
Chris

Quote from David on 14. March 2025, 11:22Hello Chris,
during execution, QBlade stores all its data in RAM. If all available RAM is utilized, the program crashes without warning.
A project file of 100GB is quite large, so my first assumption is that what you are seeing is related to RAM limitations.
Best regards,
David
Hello Chris,
during execution, QBlade stores all its data in RAM. If all available RAM is utilized, the program crashes without warning.
A project file of 100GB is quite large, so my first assumption is that what you are seeing is related to RAM limitations.
Best regards,
David
