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

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

Closed
DartBot opened this Issue Nov 9, 2014 · 11 comments

Comments

Projects
None yet
4 participants
@DartBot

DartBot commented Nov 9, 2014

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 has been minimized.

Show comment
Hide comment
@DartBot

DartBot Nov 9, 2014

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 commented Nov 9, 2014

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 has been minimized.

Show comment
Hide comment
@DartBot

DartBot Nov 9, 2014

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 commented Nov 9, 2014

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 has been minimized.

Show comment
Hide comment
@DartBot

DartBot Nov 9, 2014

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


seeing same here, Ubuntu 14.04 running 1.7.2

DartBot commented Nov 9, 2014

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


seeing same here, Ubuntu 14.04 running 1.7.2

@kasperl

This comment has been minimized.

Show comment
Hide comment
@kasperl

kasperl Nov 10, 2014

Contributor

Added Area-Editor, Triaged labels.

Contributor

kasperl commented Nov 10, 2014

Added Area-Editor, Triaged labels.

@clayberg

This comment has been minimized.

Show comment
Hide comment
@clayberg

clayberg Nov 11, 2014

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

clayberg commented Nov 11, 2014

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

@clayberg

This comment has been minimized.

Show comment
Hide comment
@clayberg

clayberg Nov 11, 2014

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.

clayberg commented Nov 11, 2014

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

This comment has been minimized.

Show comment
Hide comment
@scheglov

scheglov Nov 11, 2014

Contributor

Reproduced.


Added Accepted label.

Contributor

scheglov commented Nov 11, 2014

Reproduced.


Added Accepted label.

@scheglov

This comment has been minimized.

Show comment
Hide comment
@scheglov
Contributor

scheglov commented Nov 11, 2014

@scheglov

This comment has been minimized.

Show comment
Hide comment
Contributor

scheglov commented Nov 11, 2014

@scheglov

This comment has been minimized.

Show comment
Hide comment
@scheglov

scheglov Nov 11, 2014

Contributor

Both CL have been landed.

Thank you for the reproducible test case.


Added Fixed label.

Contributor

scheglov commented Nov 11, 2014

Both CL have been landed.

Thank you for the reproducible test case.


Added Fixed label.

@clayberg

This comment has been minimized.

Show comment
Hide comment
@clayberg

clayberg Nov 28, 2014

Added this to the 1.8 milestone.

clayberg commented Nov 28, 2014

Added this to the 1.8 milestone.

@DartBot DartBot added this to the 1.8 milestone Nov 28, 2014

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment