On 05/12/2017 03:05 PM, Blumenthal, Uri - 0553 - MITLL wrote: > > I’m not sure. It may well be that it “simply” takes all the memory > over, so there is no way for anything else to start and do the clean-up… >
Hmm, I wonder if a top(1) started before the tests would keep running, in the case that it "simply" takes all the memory over. > > > From just looking at the code, the only question that comes to mind is > whether you have a 32- or 64-bit size_t in the build environment in > question, which is unlikely to cause a eureka moment :( > > > > I can tell you that size_t is 64-bit here. It’s certainly not an > “eureka” moment for me. > > > > Some other information to check: do you have MAP_ANON defined by your > mman.h? > mman.h != mmap.h (consult 'man mmap' for authoritative header). > Todd> Yes, it’s likely this is due to the amount of memory available > in the machine. I tried to use reasonable values, but apparently not > reasonable enough > > > > Yep. In case it matters, my machine has 16GB of RAM (and runs a ton of > stuff, besides these tests :). > > Thanks. -Ben
-- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev