Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminate called after throwing an instance of 'std::bad_alloc' #131

Open
rafarohit opened this issue Sep 28, 2016 · 3 comments
Open

Terminate called after throwing an instance of 'std::bad_alloc' #131

rafarohit opened this issue Sep 28, 2016 · 3 comments

Comments

@rafarohit
Copy link

Upon executing HiFiLES, during the Flux Reconstruction Preprocessing, I find the following error (as in picture attached). Could I know what the problem means or where in the src folder I can locate std::bad_alloc?
screenshot from 2016-09-28 12-43-30

@JacobCrabill
Copy link
Member

std::bad_alloc means the code tried to allocate memory for an array, and the allocation failed. This could be due to either requesting a negative array size, or requesting more memory than is available. I would suggest checking that you aren't running out of memory first (open up system monitor to easily check while it's running).

One possible cause may be that something is wrong with your mesh or input options, and that the code is entering some unforseen state. Another cause could just be that you need to recompile (make clean && make).

@rafarohit
Copy link
Author

I can understand running out of memory. The mesh file is ~270MB. You suggested opening system memory, could you elaborate on how I can invoke that?

Furthermore, I am not sure if having the axis system defined at the center of the mesh has anything to do with the error. This means the scenario is I have inflow through a face perpendicular to the X axis on the -ve side of the axis and outflow out a face perpendicular to the X axis on the +ve side.

@rafarohit
Copy link
Author

Well, I ran system memory as I was running HiFiLES. THe memory used was over 2 GiBs which was 25% of CPU and priority was normal. Is there any indication to suggest I am running out of memory?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants