- This topic has 20 replies, 6 voices, and was last updated 20 years, 2 months ago by
.
-
Posts
-
wglass,
To follow the theme of the thread, please (if possible) send the file to [email protected] with a link to this thread so we know why we are recieving the email. Sending us test cases is the #1 best way to get something fixed. When we create test cases locally (copy-paste 100x) things still work, so we are missing a small detail that may be effecting your file that we need to test with.Done, thanks.
As a side note, raising the memory available to Eclipse (nosplash -vmargs -Xms512M -Xmx512M -XX:MaxPermSize=512M
as suggested earlier in the post) appears to have helped this morning. I’ll post a note tomorrow if this is a permanent solution.If the CSS editor has such high memory needs – maybe this should be documented? (I’ve been running alright with the Eclipse install up to now).
I don’t know if I would peg the CSS editor is the culprit, but the combination of Eclipse 3 (2x the mem requirements as Eclipse 2) plus MyEclipse 3.8.x (~130 plugins) does certainly spell the need for more memory.
Seems reasonable. Still, what puzzles me is that most of the Eclipse editors (e.g. Java) have acceptable performance, even when CSS (and XML) had these long pauses.
wglass,
We got your file (thank you) and I Just spent some time testing it and was unable to reproduce any pauses with and without the -vmargs I was using. I did notice that the memory usage jumps about 20mb when opening the file so that might be why no-args was causing the problem since E/ME on start take about 50mb and default heap space from VM is 64.Let me clarify that optimizations (speed and memory) is a constant and high priority item on our todo list. We spent a lot of time with profilers for the 3.8.2 and future releases to help trim down and tune up the WTP editors that we *digested* into ME. These editors will get better and better over time.
