Version: (using Devel) OS: OS X Installed from: Compiled sources Under mac valgrind, chromium ui tests crash horribly. Here's a log (done with --log-file=valgrind.tmp/memcheck.%p); it shows three or four different kinds of horrible crashes in different processes, all possibly related. The app itself seems to finish fine. http://build.chromium.org/buildbot/waterfall.fyi/builders/Mac%20UI%201%20of%203%20(valgrind)/builds/387/steps/valgrind%20test:%20ui/logs/stdio -- begin --- </error> findSb: can't find pointer 0xDAC8340 in arena 'client' </valgrindoutput> valgrind: the 'impossible' happened: findSb: VG_(arena_free)() in wrong arena? -- end -- or -- begin -- valgrind: m_mallocfree.c:1505 (vgPlain_arena_free): Assertion 'other_b-1 == (Block*)sb_end' failed. -- end -- or -- begin -- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting -- end -- Some of the log files simply end before any leak information is shown; perhaps that's a fourth kind of horrible crash. (Already filed that one as bug 201923, as that one also happens by itself, and on Linux as well as mac.)
(In reply to comment #0) > > -- begin --- > </error> > findSb: can't find pointer 0xDAC8340 in arena 'client' > </valgrindoutput> > valgrind: the 'impossible' happened: > findSb: VG_(arena_free)() in wrong arena? > -- end -- > > or > > -- begin -- > valgrind: m_mallocfree.c:1505 (vgPlain_arena_free): Assertion 'other_b-1 == > (Block*)sb_end' failed. > -- end -- These ones look like the heap has been corrupted, and usually that's caused by the client program. Have you fixed all the reported errors prior to this point?
I'll check.
The application is in general fairly clean; it's continuously run through its entire test suite under purify on windows and valgrind on linux and mac, and we clean up errors fairly promptly. There is a single invalid write error, but it does not occur in any of the runs that crashed. I'll check again once that has been fixed. Interesting tidbit: I ran our test suite under valgrind continuously for a few days, with each test case in a separate run, and looked at the VALGRIND INTERNAL ERROR reports. I noticed that every one went on to say valgrind: the 'impossible' happened: Killed by fatal signal <stack> <frame> <ip>0xF0130AAC</ip> </frame> Not sure what that stack is from, though.
See patch containing possible fix in bug 192634 comment #20. Feedback is solicited as I can't reproduce the problem myself, hence can't test the patch.