Eclipse bug?  
Author Message
Twisted





PostPosted: 2006-3-3 21:24:00 Top

java-programmer, Eclipse bug? Eclipse bug? Using most recent version (as of a couple weeks ago,
anyway), if it sits idle for a day or two in the taskbar, it stops
responding -- or at least it is really sluggish if you try to use it
again, and not just for a short time, but until you quit and restart it.

 
Thomas Weidenfeller





PostPosted: 2006-3-3 21:33:00 Top

java-programmer >> Eclipse bug? Twisted wrote:
> Eclipse bug? Using most recent version (as of a couple weeks ago,
> anyway), if it sits idle for a day or two in the taskbar, it stops
> responding -- or at least it is really sluggish if you try to use it
> again, and not just for a short time, but until you quit and restart it.

Report it to the eclipse people.

/Thomas
--
The comp.lang.java.gui FAQ:
ftp://ftp.cs.uu.nl/pub/NEWS.ANSWERS/computer-lang/java/gui/faq
http://www.uni-giessen.de/faq/archiv/computer-lang.java.gui.faq/
 
Twisted





PostPosted: 2006-3-4 0:13:00 Top

java-programmer >> Eclipse bug? Report it where? There's no bug report/feedback thingie inside the app
itself, so I figured a place full of Java programmers was the next best
bet -- here.

 
 
Thomas Kellerer





PostPosted: 2006-3-4 0:19:00 Top

java-programmer >> Eclipse bug? Twisted wrote on 03.03.2006 17:12:
> Report it where?

I'm not an Eclipse user, but it seems to me the link to the Bug tracker is
pretty easy to find on their homepage...

Thomas
 
 
James Westby





PostPosted: 2006-3-4 0:42:00 Top

java-programmer >> Eclipse bug? Twisted wrote:
> Eclipse bug? Using most recent version (as of a couple weeks ago,
> anyway), if it sits idle for a day or two in the taskbar, it stops
> responding -- or at least it is really sluggish if you try to use it
> again, and not just for a short time, but until you quit and restart it.
>
It's probably getting paged out of main memory. I've found that when
I've been using it, but then launch another memory heavy process for a
while then go back to it it is sluggish until all it's pages are main
memory resident again. This may be what is happening to you.


James
 
 
James McGill





PostPosted: 2006-3-4 1:04:00 Top

java-programmer >> Eclipse bug? On Fri, 2006-03-03 at 08:12 -0800, Twisted wrote:
> Report it where?

https://bugs.eclipse.org/bugs/

 
 
Twisted





PostPosted: 2006-3-4 1:17:00 Top

java-programmer >> Eclipse bug? This explains Firefox being slow or even hanging for a while after
being idle for a while, but Firefox begins to run at normal speed again
after a few moments. Eclipse requires restart. Why? Java process size
has bloated up to over 100M when this has happened. Why? Leak? Heap
fragmentation? Does hotspot VM defragment as it gcs?

 
 
Thomas Kellerer





PostPosted: 2006-3-4 1:25:00 Top

java-programmer >> Eclipse bug? James Westby wrote on 03.03.2006 17:42:
> Twisted wrote:
>> Eclipse bug? Using most recent version (as of a couple weeks ago,
>> anyway), if it sits idle for a day or two in the taskbar, it stops
>> responding -- or at least it is really sluggish if you try to use it
>> again, and not just for a short time, but until you quit and restart it.
>>
> It's probably getting paged out of main memory. I've found that when
> I've been using it, but then launch another memory heavy process for a
> while then go back to it it is sluggish until all it's pages are main
> memory resident again. This may be what is happening to you.

I thought Eclipse had fixed the problem with the paging. For JDK 1.5 there is a
(new) system property that you can set in order to prevent a minimized
application to be paged out (-Dsun.awt.keepWorkingSetOnMinimize=true)

https://bugs.eclipse.org/bugs/show_bug.cgi?id=85072

Thomas
 
 
Twisted





PostPosted: 2006-3-4 1:40:00 Top

java-programmer >> Eclipse bug? > -Dsun.awt.keepWorkingSetOnMinimize=true

Not much help if all you have to do is tab away, without minimizing,
the app for this to happen. :)

Anyway, I'm pretty sure it's more than that -- it bloats up and starts
to spend all the time GC'ing. Then again, so does anything else written
in Java, even if it's been idle all that time.

 
 
James Westby





PostPosted: 2006-3-4 3:59:00 Top

java-programmer >> Eclipse bug? Thomas Kellerer wrote:
> James Westby wrote on 03.03.2006 17:42:
>
>> Twisted wrote:
>>
>>> Eclipse bug? Using most recent version (as of a couple weeks ago,
>>> anyway), if it sits idle for a day or two in the taskbar, it stops
>>> responding -- or at least it is really sluggish if you try to use it
>>> again, and not just for a short time, but until you quit and restart it.
>>>
>> It's probably getting paged out of main memory. I've found that when
>> I've been using it, but then launch another memory heavy process for a
>> while then go back to it it is sluggish until all it's pages are main
>> memory resident again. This may be what is happening to you.
>
>
> I thought Eclipse had fixed the problem with the paging. For JDK 1.5
> there is a (new) system property that you can set in order to prevent a
> minimized application to be paged out
> (-Dsun.awt.keepWorkingSetOnMinimize=true)
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=85072
>
> Thomas

But i want this to happen, I would rather have the slight delay when it
does, than be unable to have two processes with large memory
requirements running at the same time.

The property you mention and the bug you reference are platform specific
anyway. Maybe the are applicable to the OP, so he should look in to them.


James
 
 
Scott Ellsworth





PostPosted: 2006-3-4 6:35:00 Top

java-programmer >> Eclipse bug? In article <email***@***.com>,
"Twisted" <email***@***.com> wrote:

> > -Dsun.awt.keepWorkingSetOnMinimize=true
>
> Not much help if all you have to do is tab away, without minimizing,
> the app for this to happen. :)
>
> Anyway, I'm pretty sure it's more than that -- it bloats up and starts
> to spend all the time GC'ing. Then again, so does anything else written
> in Java, even if it's been idle all that time.

Only if it is really poorly written. Frankly, gc overhead should be
pretty minimal under most circumstances for most programs. I do find
that programs which have never had a memory profile run on them often do
create a bunch of bloat and cruft, but one or two good profiles can
often fix that problem.

There are exceptions - you might generate a bunch of garbage during a
processing run, that needs cleanup once you finish, but these are
typically known times of high effort, and the flurry of gc at the end is
just part of that high effort process.

Scott

--
Scott Ellsworth
email***@***.com
Java and database consulting for the life sciences
 
 
Scott Ellsworth





PostPosted: 2006-3-4 6:44:00 Top

java-programmer >> Eclipse bug? In article <email***@***.com>,
Scott Ellsworth <email***@***.com> wrote:

> In article <email***@***.com>,
> "Twisted" <email***@***.com> wrote:
>
> > Anyway, I'm pretty sure it's more than that -- it bloats up and starts
> > to spend all the time GC'ing. Then again, so does anything else written
> > in Java, even if it's been idle all that time.
>
> Only if it is really poorly written. Frankly, gc overhead should be
> pretty minimal under most circumstances for most programs.

After I hit send, I realized that this was a bit incendiary. I was
responding to 'so does anything written in Java', rather than to Eclipse
in specific.

All programs can have bugs, and for Java programs, a common one is
letting your heap grow for no reason. The presence of such a bug does
not mean that a program is really poorly written, unless it has a _lot_
of such bugs in it, or they cannot fix the problem due to architectural
reasons. Report the bug to the Eclipse folks, and we will see how they
respond.

I do think that programs should be careful not to fill heap, and if they
do, it is likely a bug. That said, the test of whether a program is
poorly written, to me, lies in how well the architecture discourages
bugs, and how easy it makes to find and fix them.

Scott

--
Scott Ellsworth
email***@***.com
Java and database consulting for the life sciences
 
 
Twisted





PostPosted: 2006-3-4 11:50:00 Top

java-programmer >> Eclipse bug? "Memory profiling"?

 
 
Scott Ellsworth





PostPosted: 2006-3-7 4:56:00 Top

java-programmer >> Eclipse bug? In article <email***@***.com>,
"Twisted" <email***@***.com> wrote:

> "Memory profiling"?

A memory profiling tool essentially tells you what objects you are
creating, how big they are, who is holding a reference to them, and how
long they live. Most time profilers also include a memory profiling
module that can give you this information.

Running one of these can be an education - you find out whether GC is a
big part of your execution profile, and if it is, what objects are
choking it. In general, creating objects is pretty cheap, and not worth
optimizing away, and this will be even more true for Java 6. That said,
there are usage patterns that result in huge amounts of junk lying about.

There are a lot of good tools to do a memory profile. I, personally,
prefer JProfiler by e-j technologies, but YourKit also gets a lot of
good press. Both work well with IDEA, and I believe they both work well
with Eclipse, so they would also be good tools to use to profile the
IDEs themselves.

MacOS X developers also have access to the very neat Shark and
ObjectAlloc tools. I find JProfiler superior to the general tools for
most uses, but there are times where I want to know why we are getting
hit with a strange cost - is the system swapping, or calling into the
kernel. For those cases, Shark is the bee's knees.

Scott

--
Scott Ellsworth
email***@***.com
Java and database consulting for the life sciences
 
 
Twisted





PostPosted: 2006-3-22 17:24:00 Top

java-programmer >> Eclipse bug? What's a good choice that meets the following criteria:
* Works with Eclipse
* Easy to set up and use with Eclipse
* Win32 is a supported platform
* Free (as in beer; preferably as in speech too)
* Maximum functionality, subject to the above constraints

 
 
Roedy Green





PostPosted: 2006-3-23 7:14:00 Top

java-programmer >> Eclipse bug? On 22 Mar 2006 01:24:07 -0800, "Twisted" <email***@***.com> wrote,
quoted or indirectly quoted someone who said :

>What's a good choice that meets the following criteria:
>* Works with Eclipse
>* Easy to set up and use with Eclipse
>* Win32 is a supported platform
>* Free (as in beer; preferably as in speech too)
>* Maximum functionality, subject to the above constraints

but what does it do? For plug-in sources, see
http://mindprod.com/jgloss/elipse.html
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
 
 
Twisted





PostPosted: 2006-3-23 19:24:00 Top

java-programmer >> Eclipse bug? > http://mindprod.com/jgloss/elipse.html

404.

 
 
Dag Sunde





PostPosted: 2006-3-23 19:28:00 Top

java-programmer >> Eclipse bug? "Twisted" <email***@***.com> wrote in message
news:email***@***.com...
>> http://mindprod.com/jgloss/elipse.html
>
> 404.
>
Missing 'c'...
http://mindprod.com/jgloss/eclipse.html

--
Dag.



 
 
Roedy Green





PostPosted: 2006-3-24 1:46:00 Top

java-programmer >> Eclipse bug? On 23 Mar 2006 03:24:15 -0800, "Twisted" <email***@***.com> wrote,
quoted or indirectly quoted someone who said :

>> http://mindprod.com/jgloss/elipse.html
>
>404.

http://mindprod.com/jgloss/eclipse.html
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
 
 
Twisted





PostPosted: 2006-7-12 6:41:00 Top

java-programmer >> Eclipse bug? Creating a new class seems to clobber the clipboard, replacing its
contents with the class stub (that is to say, the text that is
initially in the new code tab that opens).