Bug 172739 - Null pointer crash when handling async with arrow operator
Summary: Null pointer crash when handling async with arrow operator
Status: RESOLVED DUPLICATE of bug 171274
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-30 16:31 PDT by Natalie Silvanovich
Modified: 2017-05-30 23:37 PDT (History)
4 users (show)

See Also:


Attachments
script causing the crash (209 bytes, application/javascript)
2017-05-30 16:31 PDT, Natalie Silvanovich
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Natalie Silvanovich 2017-05-30 16:31:53 PDT
Created attachment 311551 [details]
script causing the crash

The following script crashes with a null pointer exception in JSC (also attached) .

class BaseClass {
  constructor(x) {

  }

};

class DeferredSuperCall extends BaseClass {
  constructor(x) {
    return async() => super(x);
  }
};

var q =  new DeferredSuperCall("LexicalSuperCall")();
Comment 1 Saam Barati 2017-05-30 19:16:52 PDT
I think this is fixed as of today. Aleksandr, is this a dupe of what you fixed today?
Comment 2 GSkachkov 2017-05-30 23:16:46 PDT
(In reply to Saam Barati from comment #1)
> I think this is fixed as of today. Aleksandr, is this a dupe of what you
> fixed today?

Yes, it is the same as bug 171274
Comment 3 GSkachkov 2017-05-30 23:37:48 PDT
(In reply to Natalie Silvanovich from comment #0)
> Created attachment 311551 [details]
> script causing the crash
> 
> The following script crashes with a null pointer exception in JSC (also
> attached) .
> 
> class BaseClass {
>   constructor(x) {
> 
>   }
> 
> };
> 
> class DeferredSuperCall extends BaseClass {
>   constructor(x) {
>     return async() => super(x);
>   }
> };
> 
> var q =  new DeferredSuperCall("LexicalSuperCall")();

Natalie, thanks for registering this issue. We just fixed this similar bug 171274 recently. As for now I can't reproduce your issue on latest Webkit nightly build, so I'm closing this task as duplicate. 
Could you please recheck if it fixed your issue on latest WebKit nightly or latest sources?

*** This bug has been marked as a duplicate of bug 171274 ***