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
Stackoverflow in factory constructor causes Dartium to crash #19028
Comments
I don't believe the VM ever prints stack traces on uncaught stack overflows. Added Area-Editor, Triaged labels. |
cc @keertip. |
This comment was originally written by greg....@gmail.com @LRN - right - I guess the stack trace would be too big to print. It would be useful to get a trace of the bottom of the stack - so that at least you could see where the recursion began. I wonder what Java/C# do. Shall I open another bug for this? |
I'm splitting this into two bugs. I see Dartium crashing on this, and the command-line VM sending us never-ending stack frames. So for Dartium, when I run the above example I see an immediate Dartium crash, and get back a 'Inspector.targetCrashed' over the debug protocol. Set owner to @jacob314. |
Filed the VM issues as 19070. Changed the title to: "Stackoverflow in factory constructor causes Dartium to crash". |
Added Dartium-Crasher label. |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
This issue was originally filed by greg.l...@gmail.com
Running the following code causes the editor to hang, I expect the editor to show a StackOverflow error instead.
Also when running this code on the command line, no stack trace is given.
class Foo {
factory Foo.boom() => new Foo.boom();
}
main() {
new Foo.boom();
}
The text was updated successfully, but these errors were encountered: