On Sat, Aug 25, 2012 at 1:36 PM, Jim Mack <j...@less2do.com> wrote: > In a way, too many possible culprits mask each other. > > I remember a problem like this that I solved by reducing the amount of > memory so the problem would show quickly, then testing small things in > isolation and volume. Pick a subset of tests and run them multiple times at > low memory until it fails or becomes clear it won't. Rinse and repeat.
An out of memory error could also be caused by things other than a lack of memory. If the heap is getting corrupted or there is a compiler bug, the system could end up passing a garbage size to malloc or mmap that is too big to be fulfilled. -Joe ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
