You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest editor is getting itself into a state where it is consuming huge cpu resources.
A grab of the OSX process monitor showing 200+ % is attached. This wasn't transient it was sitting in this state indefinitely. It is fine when it starts. I haven't figured out what happens exactly to put it in this state.
A jstack stack trace is attached, caught when it was in this state.
Dart Editor version 0.5.20_r24275
Dart SDK version 0.5.20.4_r24275
OSX 10.8.4
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
Additional notes:
It literally roasts my iMac - the enclosure temp goes up to 90 C according to my Tunabelly Temperatue Gauge app! It also and drained the battery on my MacBook in an hour and caused its fan to come on full speed before I realized what was going on.
The example I gave you showed two of these "folding" threads stuck. It will also happen to just a single thread. I caught it busy in a single thread and grabbed the attached four stack traces to see what changed over time. Very little changes, in fact. Most of the threads are stopped waiting. The apparent busy thread ("query_norm.dart") is in the same place each time.
The "folding" thread in this case was busy with "query_norm.dart". The file was not open in my editor nor had I worked with it during that editing session, although I had worked with a file that contained a class that used it. After noticing this I went ahead and opened it and found everything worked fine, including the folding operations. Although I didn't actually edit it.
Each of the attached stacks are 5-10 seconds apart.
Here is where it appears stuck:
com.google.dart.tools.ui.text.folding.DartFoldingStructureProvider$TokenStream.begin(DartFoldingStructureProvider.java:576):
// DartFoldingStructureProvider.java at code at my last read-only snapshot
void begin(int start) {
if (start == begin) {
return;
}
if (start < begin) {
begin = 0;
currentToken = firstToken;
}
while (begin < start) { <<<<<<< HERE is line 576, this is the stuck loop it seems
currentToken = currentToken.getNext();
begin = currentToken.getOffset();
}
}
... so something in your token reader, or an odd start value?
This issue was originally filed by @jptrainor
The latest editor is getting itself into a state where it is consuming huge cpu resources.
A grab of the OSX process monitor showing 200+ % is attached. This wasn't transient it was sitting in this state indefinitely. It is fine when it starts. I haven't figured out what happens exactly to put it in this state.
A jstack stack trace is attached, caught when it was in this state.
Dart Editor version 0.5.20_r24275
Dart SDK version 0.5.20.4_r24275
OSX 10.8.4
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
Additional notes:
It literally roasts my iMac - the enclosure temp goes up to 90 C according to my Tunabelly Temperatue Gauge app! It also and drained the battery on my MacBook in an hour and caused its fan to come on full speed before I realized what was going on.
Attachments:
DartEditorCpuConsumption.jpg (31.40 KB)
jstack.out (41.83 KB)
The text was updated successfully, but these errors were encountered: