diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2016-03-22 17:02:45 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2016-03-22 17:02:45 -0700 |
| commit | d698b13f993a4af2f830bb128ad8c8652de62591 (patch) | |
| tree | a80706fc5f305de9b88978d03cee71d45be88602 /045closure_name.cc | |
| parent | 40af8c9537f158b74fba6a8d55b55d6071d8e723 (diff) | |
| download | mu-d698b13f993a4af2f830bb128ad8c8652de62591.tar.gz | |
2808 - quick fix for memory corruption
Thanks Caleb for finding this. Repeatedly running sandboxes was in some reliably reproducing situations causing 'new' to return 1, or to run into writes to the free list. No test yet; the issue is likely only mitigated at this point, not fixed. Even if routines share the Free_list, that should probably not cause memory corruption.
Diffstat (limited to '045closure_name.cc')
0 files changed, 0 insertions, 0 deletions