| commit | 89fe59c8318b2f8cec8ce00182dd24c357252c96 | [log] [tgz] |
|---|---|---|
| author | Aliaksey Kandratsenka <alkondratenko@gmail.com> | Wed Nov 29 13:37:50 2017 +0000 |
| committer | Aliaksey Kandratsenka <alkondratenko@gmail.com> | Wed Nov 29 21:44:49 2017 +0000 |
| tree | c89eb76bd039b21af837c157111302b37f4975a2 | |
| parent | a29a0cf348e131d5b8ec26c39dabeac89cf13fcd [diff] |
Fix OOM handling in fast-path Previous fast-path malloc implementation failed to arrange proper oom handling for operator new. I.e. operator new is supposed to call new handler and throw exception, which was not arranged in fast-path case. Fixed code now passes pointer for oom function to ThreadCache::FetchFromCentralCache which will call it in oom condition. Test is added to verify correct behavior. I've also updated some fast-path-related comments for more accuracy.