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

Out of memory errors can cause a segmentation fault #14431

Closed
nex3 opened this issue Oct 25, 2013 · 3 comments
Closed

Out of memory errors can cause a segmentation fault #14431

nex3 opened this issue Oct 25, 2013 · 3 comments
Labels
area-vm type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@nex3
Copy link
Member

nex3 commented Oct 25, 2013

I haven't found a way to consistently reproduce this, but I've occasionally seen segmentation faults that, when run in GDB, seem to be caused by out-of-memory exceptions.

@nex3
Copy link
Member Author

nex3 commented Oct 25, 2013

I'm also occasionally seeing this weird error in similar situations:

    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called recursively
    terminate called after throwing an instance of 'std::bad_alloc'
    terminate called recursively
      what(): std::bad_allocterminate called recursively

@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@zanderso
Copy link
Member

Was this on 32-bit? In general, we don't have a whole lot of control over what will go wrong when we're out of address space, but if you have a consistent repro feel free to re-open.

@nex3
Copy link
Member Author

nex3 commented Jun 23, 2016

I haven't seen this in a long time, so I'm okay with marking it AssumedStale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

3 participants