-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Dartium: Aw, Snap! with bad super constructor call #6064
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This comment was originally written by [email protected] Set owner to [email protected]. |
This comment was originally written by [email protected] This looks like DartVM issue. Running in DumpRenderTree (./out/Debug/DumpRenderTree --no-timeout $(realpath aw_snap.html), in aw_snap.html change dart.js script to <script>navigator.webkitStartDart()</script>), leads to assert with the following stack trace: (gdb) bt Siva, may you have a look please? cc @iposva-google. |
I was trying to reproduce an "aw, snap" with a larger program and couldn't create a minimal example for it, but stumbled on this crash:
A bad super constructor call, in some odd set of circumstances, crashes Dartium. Attached are the files in a state that crashes consistently, but I can't reduce the case much further before it become inconsistent. I'm not sure if isolates are required or not.
Not that Snap does not extend Aw like I intended when writing the code, so the super(a, b) call is wrong and should throw an error.
This is with build 13795 on OS X
Attachments:
aw_snap.dart (497 Bytes)
aw_snap.html (292 Bytes)
The text was updated successfully, but these errors were encountered: