From: Eric B. <el...@gm...> - 2007-01-31 18:14:34
|
On 1/31/07, Alan Ezust <ala...@gm...> wrote: > If your problem is specifci to JS files, then you should know there > are 2 JS parsers, the EcmaScript one is relatively new and I noticed > it does sometimes have problems with some files. If you go to plugin > options - sidekick - parsers - javascript and try switching from > ecmascript to javascript ( or vice versa ) that might solve your > problem. Alan, my problem seems to be with Markup Languages (html, jsp and xml). For me the js and java parsers are working fine, but I am using ecmascript parser for js. > > Also, since the XML plugin is actually 5 separate parsers, the memory > problems you are experiencing in SideKick may be only caused by one > specific parser and it is useful to know which parser you were using > when you ran into these types of problems. When I ran into the cpu issues, I had switched the parser for jsp from html to xml. So I'm assuming that the xml parser is the one that caused the cpu spike. The problem doesn't seem to be occurring today though, so it could have been part of a larger jvm performance issue that has since resolved itself upon restart of the machine. However, there's still an issue with the structure scope. Does anyone know if this is a known issue, or maybe something I should put on SF? Thanks for all the help. Eric -- Learn from the past. Live in the present. Plan for the future. |