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
Investigate what happens if STL allocation causes OOM #34
Comments
Comment by spetrunia I think I have accidentally hit this on a debug build. The following happened:
|
Comment by mdcallag I got that once On Sunday, May 24, 2015, Sergei Petrunia notifications@github.com wrote:
Mark Callaghan |
Comment by igorcanadi huh yeah. we never really looked at what happens when OOM. we should never corrupt the data, but rocksdb will likely crash hard. |
Comment by maykov So it is important |
Internal investigation completed. Behavior observed, documented, and understood for various scenarios. To decide if we'll change the status quo ( |
Issue by maykov
Tuesday Apr 14, 2015 at 22:48 GMT
Originally opened as MySQLOnRocksDB#52
STL relies on exceptions to handle OOM. We should check that opreator new is not overloaded to return NULL. We should also add exception handlers into all high level handler functions.
The text was updated successfully, but these errors were encountered: