Bug 357463

Summary:

[projection] Compile error can't be revealed, Line is missing

Product:

[Eclipse Project] JDT

Reporter:

Johannes Rieken <johannes_rieken>

Component:

Text

Assignee:

JDT-Text-Inbox <jdt-text-inbox>

Status:

ASSIGNED ---

QA Contact:

Severity:

normal

Priority:

CC:

daniel_megert

Version:

3.6

Keywords:

needinfo

Target Milestone:

---

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

stalebug

Attachments:

Description	Flags
where is line 48?!	none

Description Johannes Rieken

2011-09-13 06:05:46 EDT

Build Identifier: 3.7

Sometimes organize imports on save messes up my import statements - fractions of statements remain visible. Those broken lines disappear from the editor until I reopen it (see attached screen capture). I use folding of imports.

Reproducible: Sometimes

Comment 1 Johannes Rieken

2011-09-13 06:06:11 EDT

Created attachment 203230 [details]
where is line 48?!

Comment 2 Dani Megert

2011-09-13 06:12:04 EDT

>Sometimes
How often does it happen for you?

Is it just a visual problem or is the file corrupted?
What happens if you disable folding in such a situation?

As always: steps would be good :-).

Comment 3 Johannes Rieken

2011-09-13 08:04:27 EDT

This happens roughly once a week. The file is corrupted - the error in the screen capture is correct, there is a single line that reads 'eter'. There are no known steps to reproduce this, the error log is empty.

Comment 4 Dani Megert

2011-09-16 02:42:01 EDT

Hard to do anything here without more details.

Comment 5 Eclipse Genie

2020-06-02 16:16:29 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 6 Eclipse Genie

2022-07-12 13:13:29 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.