112954 2013-03-21 12:52:40 -0700 REGRESSION: Crash under createNotAnObjectError visiting SES test page 2021-05-07 13:04:54 -0700 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Mac (Intel) OS X 10.8 RESOLVED DUPLICATE 113236 http://google-caja.googlecode.com/svn/trunk/src/com/google/caja/ses/explicit.html InRadar P1 Critical --- 1 erights webkit-unassigned ap erights fpizlo ggaren oliver oldest_to_newest 860589 0 erights 2013-03-21 12:52:40 -0700 I just now installed the latest version of WebKit Nightly Version 6.0.2 (8536.26.17, 537+). It crashes the browser as a whole when visiting the SES test page at http://google-caja.googlecode.com/svn/trunk/src/com/google/caja/ses/explicit.html . The immediately previous version does fine on that page. Safari Version 6.0.2 (8536.26.17) also does fine on that page. Since the entire browser crashes, I have no idea what on that page is causing the problem. I also cannot tell for sure that the component at issue is JSC, though I expect it is. Feel free to reclassify. I'm classifying this as Critical/P1 not because I expect you think SES is that important, but because this is a browser-crashing bug. 861930 1 ap 2013-03-22 15:53:46 -0700 0 com.apple.JavaScriptCore 0x0000000108f91ad5 JSC::JSCell::toPrimitive(JSC::ExecState*, JSC::PreferredPrimitiveType) const + 21 1 com.apple.JavaScriptCore 0x0000000108f928d6 JSC::JSValue::toStringSlowCase(JSC::ExecState*) const + 886 2 com.apple.JavaScriptCore 0x0000000108dfc049 JSC::createNotAnObjectError(JSC::ExecState*, JSC::JSValue) + 57 3 com.apple.JavaScriptCore 0x0000000108df9854 JSC::JSValue::synthesizePrototype(JSC::ExecState*) const + 132 4 com.apple.JavaScriptCore 0x0000000108e55795 JSC::JSValue::get(JSC::ExecState*, JSC::PropertyName, JSC::PropertySlot&) const + 53 5 com.apple.JavaScriptCore 0x0000000108de0910 cti_op_get_by_id_generic + 80 862029 2 ggaren 2013-03-22 17:38:15 -0700 <rdar://problem/13489189> 1757967 3 erights 2021-05-07 12:51:56 -0700 That test page works fine in Safari Version 14.1 (16611.1.21.161.3). Should this be closed? 1757972 4 ap 2021-05-07 13:04:54 -0700 Thank you for the update! For some reason, this got fixed as bug 113236 without a mention here. *** This bug has been marked as a duplicate of bug 113236 ***