On Fri, 2015-04-10 at 20:04 +0000, Zhu, Yanwen wrote: > Has anyone seen this error when running valgrind 3.10.1 in a MIPS64 > platform? > > > > ==1769== Valgrind's memory management: out of memory: > > ==1769== newSuperblock's request for 4194304 bytes failed. > > ==1769== 22536192 bytes have already been allocated. > > ==1769== Valgrind cannot continue. Sorry. Not seen such a thing (but not having access to a mips platform, it is not easy to see what is going on).
What looks really strange is the very low level value of the already allocated bytes. So, maybe the aspacemgr view of the memory mapping is not in sync with the kernel view. Normally, such an OOM produces the state of the memory and the aspacemgr state. More trace would also be useful. So, can you run with -v -v -v -d -d -d and send the full log (if not too big). Also, might be useful to run with --sanity-level=4 as this will report aspacemgr<>kernel desync. Philippe ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
