Bug 147102 - REGRESSION(r187013): cannot open tddbin.com anymore "quit unexpectedly"
Summary: REGRESSION(r187013): cannot open tddbin.com anymore "quit unexpectedly"
Status: VERIFIED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-20 00:36 PDT by Tobias Reiss
Modified: 2015-07-20 13:53 PDT (History)
1 user (show)

See Also:


Attachments
Crash Report (83.40 KB, text/plain)
2015-07-20 00:36 PDT, Tobias Reiss
no flags Details
test case: defining strict arrow function (will crash on load) (58 bytes, text/html)
2015-07-20 02:13 PDT, Claude Pache
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Reiss 2015-07-20 00:36:34 PDT
Created attachment 257080 [details]
Crash Report

r187013: "quit unexpectedly - A problem repeatedly occurred with tddbin.com"
r187008: works

I would suspect https://trac.webkit.org/changeset/187012 being the cause because it's a heavy change.
tddbin.com is a "no-install/setup testing environment" from uxebu and it makes use of block scoping, const and let.
Another interesting page in that regard is http://tddbin.com/#?kata=es6/language/block-scoping/const. It offers several use cases to test block-scoping.
Comment 1 Claude Pache 2015-07-20 02:13:00 PDT
Created attachment 257083 [details]
test case: defining strict arrow function (will crash on load)

Minimal testcase: execute the following JS code in order to perform the crash:

() => { 'use strict' }
Comment 2 Claude Pache 2015-07-20 03:15:19 PDT
In fact, my testcase makes r186963 crash, while r186927 works. Either the crash of tddbin.com is unrelated to my testcase, or it was a side-effect of another change in WebKit.
Comment 3 Claude Pache 2015-07-20 03:36:47 PDT
Comment on attachment 257083 [details]
test case: defining strict arrow function (will crash on load)

Filed Bug 147105 for the issue covered by my testcase.
Comment 4 Claude Pache 2015-07-20 08:28:58 PDT
Seems to be fixed in r187018. Can you confirm (and, if yes, close the bug)?

I suspect that it was due to Bug 147105.
Comment 5 Tobias Reiss 2015-07-20 12:58:12 PDT
Yes, you're right Claude. Thanks for investigating!
Comment 6 Tobias Reiss 2015-07-20 13:53:42 PDT
Verified as fixed in latest nightly (r187018)