Skip to content
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

Avoid crashing due to ErroneousElementX #10541

Closed
peter-ahe-google opened this issue May 8, 2013 · 6 comments
Closed

Avoid crashing due to ErroneousElementX #10541

peter-ahe-google opened this issue May 8, 2013 · 6 comments
Assignees

Comments

@peter-ahe-google
Copy link
Contributor

ErroneousElementX seems to cause random crashes in places where it shouldn't. We should fix that by having it make up answers instead of crashing.

Mostly, ErroneousElementX is used to tell the backend to generate code that throws an exception. To all other users, including dartdoc, it is unfortunately a common source of crashes.

I'm pretty sure that 9917 is about ErroneousElementX, and I discovered that if you're using deferred loading, the compiler will crash if a static method is unresolved.

IIRC, Johnni was the original author, so I think he should be deciding to accept this issue or not.

Tentatively marking this as high as I generally raise the priority of crashes. Not that there's a particular crash here, but it does raise the risk of crashes as the compiler changes.

@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 Author

Removed Priority-High label.
Added Priority-Medium label.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-Later label.

@karlklose
Copy link
Contributor

The model we use now is that [Element]s can be malformed and backend ends have to check for that before asking any questions.

@kevmoo kevmoo removed the triaged label Mar 1, 2016
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

5 participants