- This topic has 28 replies, 5 voices, and was last updated 17 years, 9 months ago by
.
-
Posts
-
Now the editor loads in under 1 second where before it was taking 5-6 seconds (initial load). Also, I do not have ANY tabs, just the source view. Thanks!
Very nice.
I am using 1.6.0-b105
Yea your are good, that’s the final build of 6.0. I just don’t know what could be going on here if you have all the args in place, a clean install, and a clean workspace…
Hi, I have been getting the same problem since moving to version 5.x. I also did not have these problems in 4 and have been looking for a patch.
ssawyer,
If you aren’t using the suggested command line arguments to adjust the VM’s memory, then running into the out of memory exceptions is fairly common with even base Eclipse now. Try and tweak them and see if it helps:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-10087.htmlThis warning also popped up even though I was not interacting with Eclipse. I had started the Tomcat server via MyEclipse and was testing on a different machine. Then the warning popped up on the development machine. I had not touched Ecplise in over ten minutes.
rogue:
Was MyEclipse busy monitoring something that was running? It’s possible the debugger was doing something in the background…@support-rkalla wrote:
rogue:
Was MyEclipse busy monitoring something that was running? It’s possible the debugger was doing something in the background…I had no breakpoints set, and AFAIK MyEcplise was not active. The only activity should have been Tomcat running the application.
I am monitoring memory usage within my application with a 10 minute resolution. It has never reached above 7% unless I am manipulating images. And at any rate that should be within the Tomcat started JVM.
You stated that you are doing some rather complex memory monitoring to ensure that you do not run out of heap space. How does this differ from the memory information which the JVM provides?
Runtime.getRuntime().maxMemory()
Runtime.getRuntime().freeMemory()I am a bit confused… so far I understand the situation to be:
Computer 1: MyEclipse
Computer 2: Tomcatand MyEclipse was *not* connected as a remote debugger to Tomcat, and you walked over to Computer 2 and start running things, and then over on Computer 1 with MyEclipse you got an out of memory exception, is that right?
Computer 1 is my develpment machine. It runs Eclipse/MyEclipse. From MyEclipse I start Tomcat which runs my web application. This is all on computer one.
Computer 2 is my testing machine. I use it to run various operating systems and web browsers connecting to my development machine via http.
In the memory warning scenario above, I was doing testing using the keyboard/mouse on computer two when the warning popped up on computer one. I had not used the keyboard/mouse on computer one for over ten minutes.
I see, but if you are hosting the app (running in debug mode) on computer 1, you don’t have to be physically sitting at it for the debugger to be chewing up ram as it analyzes the running app that you are testing from computer 2.
Do you use the recommended memory arguments? We could do some profiling and digging and see what is going on
@support-rkalla wrote:
Do you use the recommended memory arguments?
Yes, as I indicated in my initial post.
This is an annoyance. It pops up and I need to dismiss it. I have never had any problems after dismissing the pop-up, even after several hours of work.
In other words I ignore the warning and nothing bad happens.
But it is annoying.
I think that I will simply have to live with it….
Do you leave MyEclipse up over night? How often does it get relaunched?
I’m just surprised if you can see this all the time that readily yet others done… do you have a ton of plugins installed or maybe just a few huge plugins (like BIRT/TPTP/etc?) or is it just a vanilla MyEclipse with nothing else? That will all contribute.
I shut down Eclipse at the end of the day (to allow for a code backup).
I install Java, Eclipse, then MyEclipse. Nothing else.
Maybe the size of the application? Though about 1000 classes is not a lot.
All this started with ME version 5.x. SOMETHING changed. And I have installed several versions of Eclipse (3.x – 3.2.1) and MyEclipse (4.x – 5.1). None of the MyEclipse 4.x gave me this message, yet every version of MyEclipse 5.x has given me the message.
