Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 106255 - [Markers] Compiler loses error and warning descriptions; blank lines in "Problems" view
Summary: [Markers] Compiler loses error and warning descriptions; blank lines in "Prob...
Status: RESOLVED DUPLICATE of bug 83992
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P2 major with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 106775 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-08-05 18:59 EDT by Andrew Hayden CLA
Modified: 2005-09-29 12:29 EDT (History)
2 users (show)

See Also:


Attachments
The normal "Problems" view. (44.43 KB, image/jpeg)
2005-08-05 19:02 EDT, Andrew Hayden CLA
no flags Details
After saving a file, having fixed a problem (42.92 KB, image/jpeg)
2005-08-05 19:04 EDT, Andrew Hayden CLA
no flags Details
After switching the filter... the problems list becomes blank. (32.85 KB, image/jpeg)
2005-08-05 19:05 EDT, Andrew Hayden CLA
no flags Details
Properties of a blank entry in the "Problems" view (16.71 KB, image/jpeg)
2005-08-05 19:07 EDT, Andrew Hayden CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Hayden CLA 2005-08-05 18:59:34 EDT
Warning: this is a real mind-bender.  I have been unable to consistently
reproduce this bug, but it happens often and is extremely annoying.  Please bear
with me:

I've got a large project here (many many thousands of files).  Occasionally,
after saving a source file or on building, my "Problems" list gets very strange
- everything is displayed properly except for the description text itself.  I've
got all the columns: but only the icons, "Resource", "In Folder" and "Location"
have anything in them.  The "Description" column is there, but there's no text.
 Anywhere.

It gets more interesting, as hovering over the problematic line in the java
editor will also NOT display the error description, which leads me to conclude
that the compiler is for whatever reason losing the description text - it's not
the "Problems" view that seems to be screwing up, as per the good old "GIGO"
principle (garbage in, garbage out).

Again, I have been unable to reproduce this in a consistent manner at this
time... HOWEVER, I have been able to SOMETIMES reproduce it by simply changing
the number of problems displayed in the view (through the filter dialog - just
changing it between 100 and 1000 and back to 100 again sometimes triggers it,
but NOT all the time).

I will make attachments showing some of this in action.  I am using Windows
2000, JDK 1.4.2, Eclipse 3.1.
Comment 1 Andrew Hayden CLA 2005-08-05 19:02:28 EDT
Created attachment 25791 [details]
The normal "Problems" view.

I am required to blur out the text.  Sorry.  This is a normal "Problems" view
in my project, before weirdness occurs.
Comment 2 Andrew Hayden CLA 2005-08-05 19:04:10 EDT
Created attachment 25792 [details]
After saving a file, having fixed a problem

This shows the "Problems" view after saving (CTRL-S), without taking ANY OTHER
ACTION, after correcting a problem in a source file.
Comment 3 Andrew Hayden CLA 2005-08-05 19:05:37 EDT
Created attachment 25793 [details]
After switching the filter... the problems list becomes blank.

After swapping the filter a couple times, this is what happens.  All the
descriptions are gone.	Doing a complete clean and rebuild will NOT recover the
descriptions.  Nor will switching the filter.  At least, not consistently.
Comment 4 Andrew Hayden CLA 2005-08-05 19:07:00 EDT
Created attachment 25794 [details]
Properties of a blank entry in the "Problems" view

Right-clicking and choosing "Properties" for an item in the "Problems" view
makes this show up.  Note that the description line in the dialog is blank. 
Hovering over the line in the source file will not bring up a tooltip any more,
either.
Comment 5 Andrew Hayden CLA 2005-08-05 19:08:12 EDT
I apologize for the many attachments but I want to make sure this bug is not
confused with other, similar bugs.  Such similar bugs that are NOT duplicates of
this (as far as I can gather) seem to be 86329, 92771, 93488, 45381, 46604, and
101299.  This is an odd one.

Good luck, guys!  Wish I had a clue how to fix this one!
Comment 6 Olivier Thomann CLA 2005-08-07 22:11:58 EDT
Move to Platform/UI
Comment 7 Philipe Mulet CLA 2005-08-12 05:08:42 EDT
*** Bug 106775 has been marked as a duplicate of this bug. ***
Comment 8 Darin Swanson CLA 2005-08-12 10:29:57 EDT
Moving to major as this really impedes our productivity.
In our lab problem seen on both windows and linux.
Comment 9 Peter Booth CLA 2005-09-07 09:55:49 EDT
(In reply to comment #8)
> Moving to major as this really impedes our productivity.
> In our lab problem seen on both windows and linux.

This is a stuningly painful bug and I have reverted to 3.02 so I can develop as this gets fixed. Does anyone 
have any news of a workaround?
Comment 10 Tod Creasey CLA 2005-09-07 10:05:32 EDT
Darin do you have a replicatale case? I'm afraid I have never seen it here.
Comment 11 Andrew Hayden CLA 2005-09-07 10:09:39 EDT
(In reply to comment #10)
> Darin do you have a replicatale case? I'm afraid I have never seen it here.

I can get this to occur by switching the number of displayed items around in my
filter, as noted in the original report - try switching back and forth between
100 and 1000 a few times, and hopefully it will crop up...
Comment 12 Tod Creasey CLA 2005-09-07 10:46:13 EDT
Darin are you using 2000 or XP? 

I can't replicate on XP with a workbench with about 2000 errors and warnings
using 3.1.1.

Also can you make it go away by restarting?
Comment 13 Darin Swanson CLA 2005-09-07 11:02:35 EDT
XP and restarting did not reliably fix the problem.
Others in our group have seen it on Linux as well.
Comment 14 Andrew Hayden CLA 2005-09-07 11:08:31 EDT
It persists across startups, so no, it does not go away by closing and reopening.

I am experimenting with a fresh Eclipse install and a junk project to see if I
can find some way to consistently reproduce this error; so far, no luck.

I wonder if the other folks on the CC: for this thread could assist me in trying
to find some common factors...

A little more detail about my project:
* Workspace resides on local hard drive
* Project resides on Samba mount point on UNIX system
* ~100 jars on the classpath as a user library
* ~70 source directories on the classpath
* Compiling under 1.4 rules
* Project is "shared" (initially checked out from CVS using Eclipse)

I'll continue trying to replicate using a standalone project... no luck so far,
though.
Comment 15 Yves Canty CLA 2005-09-07 11:36:39 EDT
We are also experiencing this problem, and I haven't found a way to consistently
reproduce it either.

Our projects are also shared, but with Clearcase.  My workspace is as follows:

- Eclipse 3.1.0 Build id: I20050627-1435
- 16 projects loaded (all stored in clearcase)
- Projects have dependencies with each others. There are also some circular
dependencies between them.
- using a clearcase snapshot view on the c: drive (but I've seen the problem
using dynamic views on network drives too)
- Compiling under 1.5 rules
- ~35 source directories on the classpath, and maybe around 50 jars.
- Problem view Filter set to 1000 items
- The total # of Problems (warnings) is 25,547

The problem seems to have more chance of happening when there are compilation
errors in the workspace. Especially when there are inter-project discrepancies.
The last time it happened to me, someone had renamed a project and somehow
eclipse had a hard time picking up the change when I used an old team project
set to import all the projects.  I fixed it by deleting all projects,
reimporting them through an updated team project set, cleaning all projects and
doing a full rebuild.

I also tried reproducing it with a few small, dummy projects, with no luck... 
I'll post an update the next time it happens to me, if I can figure out the
special conditions that make it happen...
Comment 16 Yves Canty CLA 2005-09-08 16:14:32 EDT
I have just reproduced the bug in my environment described previously.

- Turn off "build automatically"
- Clean all projects (do not start a build)
- Update my clearcase snapshot view, thus updating some workspace source files,
adding new ones, etc.
- select all projects from the package explorer
- Press F5 to refresh them
- Turn on "build automatically".  Wait for the build to finish.

The build then has 3 errors (with description) about missing resources and such
(which was expected after this refresh), and 981 warnings.  975 warnings are
from the RMI plugin we're using, and they have descriptions.  6 warnings seem to
be from the eclipse compiler, and have only the icon and "Resource" columns
filled in. The other columns are blank.

Note that one particularity of this refresh is that one of the projects changed
name (new <name> in its .project).  Workspace refresh didn't pick that up, so it
still shows the old name in the package explorer, and that is the cause of the 
3 compilation errors.  Maybe a change to .project outside of workspace control,
followed by a workspace refresh, is a way to trigger this "no description" bug?
Comment 17 Garth Dahlstrom CLA 2005-09-19 11:57:21 EDT
I've also encountered this problem...  very frustrating...  Our project
generates about 1,500 warnings.   When I use JLint for eclipse we get up to
about 4600, changing some filter settings often results in loss of descriptions. :(

Doing a Clean followed by a rebuild will get them back.  (Otherwise they stay
blank between rebuilds and IDE restarts)

I've also notice that this can happen on a smaller scale where 2 or 3 warning
descriptions are blank, not sure if this is related (perhaps eclipse is not
parsing the javac output for those vs. missplacing all the message descriptions
later).
Comment 18 Tod Creasey CLA 2005-09-29 12:29:28 EDT

*** This bug has been marked as a duplicate of 83992 ***