Skip to content

Dart2JS's unwrapException appears to be fragile #7545

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

Closed
blois opened this issue Dec 20, 2012 · 11 comments
Closed

Dart2JS's unwrapException appears to be fragile #7545

blois opened this issue Dec 20, 2012 · 11 comments
Assignees

Comments

@blois
Copy link

blois commented Dec 20, 2012

unwrapException relies on the message of the exception to determine what type of Dart exception object it should be, but this appears to be fragile and prone to changes in browsers.

For example, Chrome appears to have recently changed the message when functions cannot be found.

@peter-ahe-google
Copy link
Contributor

Added Duplicate label.
Marked as being merged into #3313.

@peter-ahe-google
Copy link
Contributor

Upon further consideration, I think the problem is our interceptor implementation. Pete: could you provide an example or a bad stack trace?


Set owner to @peter-ahe-google.
Added this to the M3 milestone.
Added NeedsInfo label.
Marked as being merged into #.

@ErikCorryGoogle
Copy link
Contributor

Possible fix was committed here:
https://codereview.chromium.org/11645050/

@blois
Copy link
Author

blois commented Dec 21, 2012

Correct, also see:
https://codereview.chromium.org/11644053/

Latest Chrome developer builds changed the error's message and also removed some of the properties so it now looks much more like FireFox.

This was the source of the failures in build:
http://chromegw.corp.google.com/i/client.dart/builders/dart2js-chrome-linux/builds/1971

Note that we only saw these errors yesterday on the Linux Chrome dev builds, but I assume it will be rolling out more widely.

@peter-ahe-google
Copy link
Contributor

Do we know why Chrome removed these properties? Aligning with Firefox is suboptimal for compiling other languages to JavaScript. We need to get some kind of error code, precisely like Internet Explorer provides or Chrome used to provide. Relying on localized strings is dreadful :-(

@blois
Copy link
Author

blois commented Dec 21, 2012

I don't have any background on Chrome's change though the new behavior appears to be a closer implementation of the js language spec.

@peter-ahe-google
Copy link
Contributor

Removed this from the M3 milestone.
Added this to the M4 milestone.

@kasperl
Copy link

kasperl commented Apr 22, 2013

Removed this from the M4 milestone.
Added this to the M5 milestone.

@kasperl
Copy link

kasperl commented May 23, 2013

Added TriageForM5 label.

@kasperl
Copy link

kasperl commented May 28, 2013

Removed this from the M5 milestone.
Added this to the Later milestone.
Removed TriageForM5 label.

@peter-ahe-google
Copy link
Contributor

Fixed in r25262.


Added Fixed label.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants