DartEditor 100% all core cpu utilization & large memory usage on specific code sample (included)

[DartBot]

This issue was originally filed by @mulander

---

What steps will reproduce the problem?

1. Download Chapter_05.tar.gz
2. Unpack
3. Start the Dart Editor and File -> Open existing folder

What is the expected output? What do you see instead?
I expect the project to be loaded, quickly analyzed and workable.

Instead all my cores go to 100% CPU utilization, 2 gigs of memory usage and keeps spinning without ever ending (waited for 0.5h top).

What version of the product are you using?

Me:
 Dart Editor version 1.7.2.release (STABLE)
 Dart SDK version 1.7.2

Friend:
 Dart Editor version 1.7.2.release (STABLE)
 Dart SDK version 1.7.2

On what operating system?
Me: Archlinux 64-bit
Friend: 64bit Slackware Linux

What browser (if applicable)?
Not relevant

Please provide any additional information below.
The code is a slightly modified Chapter_05 example from the official tutorial. I include both my modified code & a git diff from the whole repository. I don't know what change introduced the problem.

I asked a friend to test on his instance and he reports the same issue (cpu usage at 100%, high mem - not ending)

---

Attachments:
Chapter_05.tar.gz (1.80 MB)
changes.diff (18.82 KB)

[DartBot]

This comment was originally written by thomas.granvej...@gmail.com

---

I've tried this on a Slackware 14.1 x86_64 box running 1.7.2 and I can confirm that the editor/analyzer goes bananas. After 5 minutes of 100% maxed out cores, I killed the editor.

[DartBot]

This comment was originally written by @mezoni

---

I think the (editor) authors will tell you, "This is impossible, we have several times fix this".

[DartBot]

This comment was originally written by craigvan...@gmail.com

---

seeing same here, Ubuntu 14.04 running 1.7.2

[kasperl]

Added Area-Editor, Triaged labels.

[clayberg]

Set owner to @scheglov.
Removed Priority-Unassigned label.
Added Priority-Medium label.

[clayberg]

Andrew - We will test this using 1.7.2 and 1.8.0 to see whether we can reproduce it, and whether we have fixed it in the latest build . If we haven't fixed it, we will fix it as quickly as possible. We have fixed other 100% CPU utilization cases in the past, and we plan to fix any that are reported to us in the future. I'm sure you understand that there can be multiple causes for seeing a 100% utilization. Reproducing and fixing one or more cases, does not mean we have fixed all possible cases, nor does it mean that we aren't interested in test cases that illustrate new cases now and in the future. Specific code examples like this are extremely useful to us, so we encourage future bg reporters to do exactly what this reported did with this case.

[scheglov]

Reproduced.

---

Added Accepted label.

[scheglov]

CL for Java: https://codereview.chromium.org/713303002

---

Added Started label.

[scheglov]

CL for Dart: https://codereview.chromium.org/717723003

[scheglov]

Both CL have been landed.

Thank you for the reproducible test case.

---

Added Fixed label.

[clayberg]

Added this to the 1.8 milestone.