Comment 16 for bug 1007082

Ken, thanks for testing and confirming. So while the overall issue remains the same (system detects that a page from some cache pool is not properly initialized), the latest trace shows at least that the exact nature of the corruption may not be consistent. This likely will be hard to get down to...