* SUMMARY Bug 16220 Comment #4 using WebKit nightly r28314 on a webarchive of www.news.com and Bug 16223 Comment #12 using WebKit nightly r28383 on digg.com have very similar stack traces. I don't know how to reproduce this crash yet. * STEPS TO REPRODUCE See comments in other bugs. Browsing around digg.com or loading the webarchive from bug 16220 may reproduce the issue. * REGRESSION Most likely a regression. * NOTES Perhaps there is a different memory smasher at work here?
Haven't seen this in many months. Closing as WORKSFORME (since there is no CANNOTREPRODUCE).