39803 2010-05-26 18:38:58 -0700 REGRESSION: Crashes every time at www.modbee.com 2010-05-26 23:02:33 -0700 1 1 1 Unclassified WebKit Layout and Rendering 528+ (Nightly build) Mac (Intel) OS X 10.6 RESOLVED DUPLICATE 39788 http://www.modbee.com P1 Major --- 1 caesar3740 webkit-unassigned ap hyatt mitz oldest_to_newest 231038 0 caesar3740 2010-05-26 18:38:58 -0700 Using version 6531.22.7, r60253 of Webkit, www.modbee.com crashes every time I try and visit the site. Not sure why. 231115 1 ap 2010-05-26 22:54:56 -0700 Confirmed with r60253. Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 ??? 000000000000000000 0 + 0 1 com.apple.WebCore 0x0000000100feda8c WebCore::RenderLayer::updateLayerPositions(unsigned int, WebCore::IntPoint*) + 44 2 com.apple.WebCore 0x0000000100fedbce WebCore::RenderLayer::updateLayerPositions(unsigned int, WebCore::IntPoint*) + 366 3 com.apple.WebCore 0x0000000100fedbce WebCore::RenderLayer::updateLayerPositions(unsigned int, WebCore::IntPoint*) + 366 4 com.apple.WebCore 0x0000000100fedbce WebCore::RenderLayer::updateLayerPositions(unsigned int, WebCore::IntPoint*) + 366 5 com.apple.WebCore 0x0000000100a5f6e7 WebCore::FrameView::layout(bool) + 1271 6 com.apple.WebCore 0x00000001009199e4 WebCore::Document::updateLayoutIgnorePendingStylesheets() + 52 7 com.apple.WebCore 0x0000000100858ec9 WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue(int, WebCore::EUpdateLayout) const + 297 8 com.apple.WebCore 0x00000001008627c6 WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue(int) const + 22 9 com.apple.WebCore 0x000000010085796b WebCore::CSSComputedStyleDeclaration::getPropertyValue(int) const + 27 10 com.apple.WebCore 0x00000001008a73f0 WebCore::CSSStyleDeclaration::getPropertyValue(WebCore::String const&) + 80 11 com.apple.WebCore 0x0000000100bd4bed WebCore::jsCSSStyleDeclarationPrototypeFunctionGetPropertyValue(JSC::ExecState*, JSC::JSObject*, JSC::JSValue, JSC::ArgList const&) + 205 231118 2 ap 2010-05-26 23:02:33 -0700 I'm told that this is a duplicate of bug 39788, should be fixed in the next nightly build. *** This bug has been marked as a duplicate of bug 39788 ***