CFD Online Discussion Forums

CFD Online Discussion Forums (
-   CFX (
-   -   Return code 255 (CFX-5.7.1) (

Jesper May 20, 2005 05:17

Return code 255 (CFX-5.7.1)
Hi, The solver closes down suddently with a return code 255 and an additional message saying that their is not enough memory. Could this be because of a large output file? If so, is their a way to reduce the size of the file? Regards Jesper

Rui May 20, 2005 11:47

Re: Return code 255 (CFX-5.7.1)

What is exactly the message? Copy it from the .out file and paste here.

What is the size of the .out file? I working on a PC with Pentium 4 and 512 MB Ram, and I have had .out files larger than 100 MB without any problem (except that the simmulation takes ages).

What type of simmulation are you performing?



Tim Guo May 22, 2005 04:03

Re: Return code 255 (CFX-5.7.1)
Hi, same condition happened to me when I set the particle tracking information in the Solve Control too big. I checked my working directory in which all disk space is filled. You are setting somewhere got problem.

Tim Guo May 22, 2005 04:04

Re: Return code 255 (CFX-5.7.1)
Your setting somewhere got problem.

Jesper May 23, 2005 08:03

Re: Return code 255 (CFX-5.7.1)
Hi, Then it might not be the size of the out file anyway. The error message I am referíng to was written in the little command window that opens up with solver. Unfortunately it did not copy it. But it was an "out of memory" message, and to me it seemed like the solver had somehow run out of memory. A gui-error is stored in the library of the simulation, with the information:


Title = An error has occurred in cfx5solve:

Level = ERROR

Message = "The CFX-5 solver has terminated without writing a results file. Command on", "host blue6 exited with return code 0." END END

I am running a paralelle simulation, and opening up the task manager in the start of the run showed plenty of memory left in the RAM. I have made an auto backup of the results, so their is no problem starting up the simulation again from that filw. When restarting the simulation, it stops again after approx. the same number of iterations (11,000, now 22,000...)

Regards Jesper

All times are GMT -4. The time now is 19:11.