On Tue, Aug 4, 2009 at 5:14 PM, Adam Langley<a...@chromium.org> wrote: > On Tue, Aug 4, 2009 at 5:11 PM, Peter Kasting<pkast...@google.com> wrote: >> That is probably coming from the allocator underneath Chrome (presumably the >> one provided by the OS kernel). It probably means you have memory >> corruption that eventually leads to this. > > Yea, it does look a lot like it's from the kernel - but I don't think > it is. SLAB was the kernel's default memory allocator for a long time, > but SLAB_MAGIC isn't from the kernel sources (at least going back to > 2005).
Grepping every file on the system was the obvious thing to do; it found /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore So I guess some memory corruption bug (ours?) stepped on a slab used by Quartz. - Dan --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---