zherczeg at inf.u-szeged.hu
Fri Dec 17 00:02:43 PST 2010
>> On 6 December 2010 22:31, Zoltan Herczeg <zherczeg at inf.u-szeged.hu>
>> > Crash in WTF::fastMalloc? Such things only happen if something
>> > memory areas belongs to the memory manager (i.e overwrites some bytes
>> > before or after a block returned by malloc). Try some valgrind
>> > on mac to detect those writings into "red zones".
>> How can you use valgrind to help on that? We had some symptoms similar
>> to this and also came to the conclusion that probably something is
>> overwriting the structures used by fast malloc, but couldn't find
>> anything with valgrind. Overwriting in an area that has bee reserved
>> is not an error vangrind finds, at least not with any options that I
I haven't received your reply before. To capture this bug, you have to
disable fastmalloc, and use the internal (trackable) memory allocator
replacement of valgrind.
Run "build-webkit --system-malloc"
This will redirect all allocations to the system malloc.
More information about the webkit-dev