[chromium-dev] Re: Mystery error "Assertion failed: (slab->magic == SLAB_MAGIC), function slab_alloc, file x-alloc.c, line 353."

2009-08-05 Thread Dan Kegel
On Tue, Aug 4, 2009 at 5:14 PM, Adam Langley wrote: > On Tue, Aug 4, 2009 at 5:11 PM, Peter Kasting 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 th

[chromium-dev] Re: Mystery error "Assertion failed: (slab->magic == SLAB_MAGIC), function slab_alloc, file x-alloc.c, line 353."

2009-08-04 Thread Adam Langley
On Tue, Aug 4, 2009 at 5:11 PM, Peter Kasting 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 -

[chromium-dev] Re: Mystery error "Assertion failed: (slab->magic == SLAB_MAGIC), function slab_alloc, file x-alloc.c, line 353."

2009-08-04 Thread Peter Kasting
On Tue, Aug 4, 2009 at 5:03 PM, Dan Kegel wrote: > Twice now (three days ago and today) I got the error > Assertion failed: (slab->magic == SLAB_MAGIC), function slab_alloc, > file x-alloc.c, line 353. > while running the ui tests under valgrind on the mac... > and I can't figure out where it's c