Memory release after killing the run

nisha · November 20, 2013, 04:07

I am using OpenFOAM 2.1.x on Ubuntu platform. When a run is 'killed', the RAM still shows as used up. Starting a new run gives an error: 'cannot satisfy memory request' which I assume is due to lack of free space on RAM.

However, when the run 'stops' itself (i.e., solver reaches the prescribed end time), the RAM is released.

Currently, I need to restart the machine to recover the RAM. Any ideas to recover the RAM after 'killing' the run ?

akidess · November 20, 2013, 04:39

How exactly are you "killing" the run?

nisha · November 27, 2013, 00:12

Sorry for delay in my reply.

I am killing the run by following ways:
1. Ctrl + C at teminal
2. Specifying the time to stop at controlDict/stopAt
3. Specifying noWriteNow or writeNow at controlDict/stopAt

All three methods yield same result : memory is shown as used.

akidess · November 27, 2013, 04:38

How do you start the solver? Do the processes still appear in the process list after the interrupt (Ctrl+C)?

nisha · November 27, 2013, 07:17

Starting the solver in parallel mode as:
mpirun -np 12 icoFoam -parallel >& log

The process is killed successfully with Ctrl+C and do not show up in the list.

November 20, 2013, 04:07	Memory release after killing the run	#1
nisha New Member Nisha Join Date: Sep 2009 Location: Massachusetts Posts: 18 Rep Power: 17	I am using OpenFOAM 2.1.x on Ubuntu platform. When a run is 'killed', the RAM still shows as used up. Starting a new run gives an error: 'cannot satisfy memory request' which I assume is due to lack of free space on RAM. However, when the run 'stops' itself (i.e., solver reaches the prescribed end time), the RAM is released. Currently, I need to restart the machine to recover the RAM. Any ideas to recover the RAM after 'killing' the run ?

November 20, 2013, 04:39		#2
akidess Senior Member Anton Kidess Join Date: May 2009 Location: Germany Posts: 1,377 Rep Power: 30	How exactly are you "killing" the run? __________________ On twitter @akidTwit Spend as much time formulating your questions as you expect people to spend on their answer.

November 27, 2013, 04:38		#4
akidess Senior Member Anton Kidess Join Date: May 2009 Location: Germany Posts: 1,377 Rep Power: 30	How do you start the solver? Do the processes still appear in the process list after the interrupt (Ctrl+C)? __________________ On twitter @akidTwit Spend as much time formulating your questions as you expect people to spend on their answer.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Case running in serial, but Parallel run gives error	atmcfd	OpenFOAM Running, Solving & CFD	18	March 26, 2016 13:40
Openfoam Ubuntu 12.04 Unmet dependencies	slls33	OpenFOAM Installation	10	April 9, 2013 05:16
Run-time memory allocation error with 40GB RAM	juanmariacg	CFX	10	October 25, 2012 06:59
How to optimize the memory usage when using FEM	vasilis	Main CFD Forum	11	August 25, 2009 00:57
CFX Run out of memory	Lucas	CFX	0	January 22, 2009 20:42

November 27, 2013, 00:12		#3
nisha New Member Nisha Join Date: Sep 2009 Location: Massachusetts Posts: 18 Rep Power: 17	Sorry for delay in my reply. I am killing the run by following ways: 1. Ctrl + C at teminal 2. Specifying the time to stop at controlDict/stopAt 3. Specifying noWriteNow or writeNow at controlDict/stopAt All three methods yield same result : memory is shown as used.

November 27, 2013, 07:17		#5
nisha New Member Nisha Join Date: Sep 2009 Location: Massachusetts Posts: 18 Rep Power: 17	Starting the solver in parallel mode as: mpirun -np 12 icoFoam -parallel >& log The process is killed successfully with Ctrl+C and do not show up in the list.