Comment 3 for bug 367744

@arturj -- The symptom implies that slub went to return some memory to the main allocator that does not appear (at least at the time the free occured) to have belonged to slub. Either slub freed it earlier or someone who should not have (outside slub) has freed it without slub's knowledge. Bad. is this reproducible? ie. does it occur often on resume from suspend or is this a one off? if it is not reproducible we are very unlikely to be able to find it via debug.