Comment #16 on issue 28749 by [email protected]: renderer crash in malloc http://code.google.com/p/chromium/issues/detail?id=28749
Unfortunately even with the backtrace from comment #14 after staring at bits of the code I'm not seeing an obvious cause for the memory corruption or recent changes in those areas. I didn't work my way down the whole call chain though ... it is pretty long. Arguably that backtrace is showing where the corruption triggered a problem, not necessarily where the corruption happened initially. I'm also running into valgrind mmap failed issues (similar to issue 28439) so I can't pump this through valgrind. Joel: can you try valgrinding this on 64 bit please where hopefully the valgrind 1Gig issue might not be a problem. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
