Bug 231462 - Exception in Compiler Reader thread
Summary: Exception in Compiler Reader thread
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: 3.5 M1   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-11 11:18 EDT by Luiz Fernando Oliveira Corte Real CLA
Modified: 2008-08-06 15:08 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luiz Fernando Oliveira Corte Real CLA 2008-05-11 11:18:32 EDT
Build ID: I20080502-0100

Steps To Reproduce:
1. Open Eclipse with some projects already open (I had 65 open, from the project Archimedes - the open CAD)
2. Wait for the compiler to start building the workspace


More information:
When Eclipse starts building the workspace, the following error message is sent to console:

Exception in thread "Compiler Source File Reader" org.eclipse.jdt.internal.compiler.problem.AbortCompilation
	at org.eclipse.jdt.internal.core.builder.SourceFile.getContents(SourceFile.java:81)
	at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:151)
	at java.lang.Thread.run(Thread.java:619)
Exception in thread "Compiler Source File Reader" org.eclipse.jdt.internal.compiler.problem.AbortCompilation
	at org.eclipse.jdt.internal.core.builder.SourceFile.getContents(SourceFile.java:81)
	at org.eclipse.jdt.internal.compiler.ReadManager.run(ReadManager.java:151)
	at java.lang.Thread.run(Thread.java:619)

I have already tried to refresh and clean the project, but it still continues. It is not specific for one project.
Comment 1 Luiz Fernando Oliveira Corte Real CLA 2008-05-11 12:31:19 EDT
Did not happen after rebuilding projects inside Eclipse 3.3
Comment 2 Philipe Mulet CLA 2008-05-12 05:32:11 EDT
Could be an encoding issue surfacing, but mishandled in concurrent compiler.
Comment 3 Kent Johnson CLA 2008-05-12 09:27:41 EDT
Please try a recent nightly build.

We released a fix for bug 229480, so we should get better error reporting
from now on.

thx
Comment 4 Kent Johnson CLA 2008-05-13 11:59:50 EDT
I've thrown some exceptions from SourceFile.getContents() & with the fix for bug 229480, we're correctly reporting them as build errors.

I suggest we close this as WorksForMe, unless Luiz can confirm that he still has a problem with the lastest build.
Comment 5 Luiz Fernando Oliveira Corte Real CLA 2008-05-13 20:13:08 EDT
(In reply to comment #4)
> I've thrown some exceptions from SourceFile.getContents() & with the fix for
> bug 229480, we're correctly reporting them as build errors.
> 
> I suggest we close this as WorksForMe, unless Luiz can confirm that he still
> has a problem with the lastest build.
> 

I will download the latest Integration version tomorrow and try to reproduce the bug.

Another detail that may be relevant is that I had updated the projects outside Eclipse (by 'svn update') before that bug appeared. Before that, it was working normally for me.
Comment 6 Luiz Fernando Oliveira Corte Real CLA 2008-05-14 20:01:28 EDT
I couldn't reproduce the bug neither in build I20080513-2000 nor in the build I20080502-0100, which was the build with that bug originally. I think it may happened for a specific update for the project which I was working on.
Comment 7 Philipe Mulet CLA 2008-05-16 05:13:18 EDT
Might want to keep this bug open until 3.4 end... 
Comment 8 Jerome Lanneluc CLA 2008-05-16 05:34:36 EDT
Kent, please close early 3.5 if it still cannot be reproduced.
Comment 9 Philipe Mulet CLA 2008-06-03 07:21:55 EDT
Reducing severity, since it cannot be considered as a blocker if not reproduceable any longer.
Comment 10 Kent Johnson CLA 2008-07-29 10:42:23 EDT
We believe this was fixed 2 months ago with the change for bug 229480 (released in 3.4 RC1) & have not received any similar bug reports since then.
Comment 11 Olivier Thomann CLA 2008-08-06 15:08:58 EDT
Verified for 3.5M1 using I20080805-1307