WebKit revision 19461, --debug build, on a PowerBook G4, running Mac OS X 10.4. I run the page load test at http://www.cs.umd.edu/projects/PL/beep/topN_web.pltsuite by placing it /Applications/Safari.app/Contents/Resources. I then chose the options "Web-Kit-only window", "Clear cache before each page" and "Run test once". After loading the first six or seven pages, WebKit either causes a segmentation violation at WebCoreSupport/WebFrameLoaderClient.mm:891 or causes an assertion failure at loader/Cache.cpp:163
(In reply to comment #0) > After loading the first six or seven pages, WebKit either causes a segmentation > violation at WebCoreSupport/WebFrameLoaderClient.mm:891 or causes an assertion > failure at loader/Cache.cpp:163 The assertion failure is covered in Bug 12652. Please post the stack trace (may be found in ~/Library/Logs/CrashReporter/Safari.crash.log--no need to post the whole file, just the stack for the WebFrameLoaderClient.mm:891 crash).
(In reply to comment #1) > (In reply to comment #0) > > After loading the first six or seven pages, WebKit either causes a segmentation > > violation at WebCoreSupport/WebFrameLoaderClient.mm:891 or causes an assertion > > failure at loader/Cache.cpp:163 > > The assertion failure is covered in Bug 12652. Please post the stack trace > (may be found in ~/Library/Logs/CrashReporter/Safari.crash.log--no need to post > the whole file, just the stack for the WebFrameLoaderClient.mm:891 crash). > Nikhil, as David said, we need the crash log to proceed with this report. In current state the bug report is INVALID. Feel free to reopen the bug if the crash still happens to you, but please remember to attach requested information.