From: Eric B. <el...@gm...> - 2007-02-01 16:13:30
|
On 1/31/07, Dale Anson <da...@gr...> wrote: > It is most likely the Ecmascript parser that is causing the problems. As > was mentioned on this thread, it is relatively new. There are already a > couple of bugs entered against it, but getting them fixed is difficult > since there seem to be a couple of different scenarios that cause the > problem. > > One thing you might not know is that the HTML parser delegates to both the > CSS parser and the Ecmascript parser to handle <style> and <script> tags > inline in an html file. So while you may be looking at an html file with > the html parser selected, it could indeed be the Ecmascript parser choking > on some inline javascript in your html. The css, ecmascript, and html > parsers are all part of the XML plugin. Hi Dale, Thanks, this actually explains quite a bit for me. Do you know if the HTML parser delegates to which ever parser you have under javascript and css? So, if I change the parser for javascript to "javascript" instead of "ecmascript" it'll delegate to the "javascript" parser instead? In regards to the extraordinary CPU usage one day, and nearly none the next. I noticed something last night with the OpenIt plugin. My CPU spikes from 1-2% (normal) to 60-100% when it's indexing the files. It's possible that OpenIt was indexing and the js parser added another spike, and something just got stuck (maybe some sort of disc contention). I had OpenIt indexing my entire development directory which contains about 6 full projects. I had the refresh rate set to 1 minute, and it's entirely possible that it was taking longer than 1 minute to index the entire directory. So my thought is that OpenIt was just continuously indexing, and the sidekick plugin just added to the fire. I have since reduced the refresh rate to 5 minutes, and restricted the path to the current projects files. This seems to have fixed the cpu issue for me at least. I will keep watching though. Thank you everyone for the help. Eric -- Learn from the past. Live in the present. Plan for the future. |