Hi
VM should only use part of the resources. I usually give about 2/3 of the maximum available resources. If you have just two cores there is not much to choose there so I think you're fine. For large jobs memory may be a bottle-neck and that sometimes leads to abrupt core dumps. Many libraries don't much test whether there is memory available. For that reason I have 16 Gb of memory on my laptop.
-Peter
Elmer Command-Line Workflow -> Program received signal SIGSEGV
Re: Elmer Command-Line Workflow -> Program received signal SIGSEGV
As mentioned in previous posts, the
error
happens due to many known and unknown reasons that finally leads the solver to stop running.
I have encountered the errors for the following reasons:
1. Large mesh size compared to the available memory of computer. I used to solve this by using a coarser mesh.
2. Using shared object(.so) files of user defined solvers /functions compiled by elmerf90 in another computer using different version of the OS. This error disappeared after recompiling the user defined functions with elmerf90 fortran compiler of the currently installed Elmer software.
error
Code: Select all
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
happens due to many known and unknown reasons that finally leads the solver to stop running.
I have encountered the errors for the following reasons:
1. Large mesh size compared to the available memory of computer. I used to solve this by using a coarser mesh.
2. Using shared object(.so) files of user defined solvers /functions compiled by elmerf90 in another computer using different version of the OS. This error disappeared after recompiling the user defined functions with elmerf90 fortran compiler of the currently installed Elmer software.
Anil Kunwar
Faculty of Mechanical Engineering, Silesian University of Technology, Gliwice
Faculty of Mechanical Engineering, Silesian University of Technology, Gliwice