Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332653

Summary:

editor contents become corrupted after many quick undo actions

Product:

[Eclipse Project] JDT

Reporter:

Nicolas Bros <nicolas.bros>

Component:

Text

Assignee:

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

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

CC:

daniel_megert

Version:

3.7

Keywords:

needinfo

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
configuration	none

Description Nicolas Bros

2010-12-15 11:04:09 EST

Often, when I have made many changes and I try to undo a lot of changes at once, I keep the "Ctrl+Z" keys pressed for a few seconds, which triggers a lot of modifications in a short amount of time.
After this, I often find that the contents of the editor have become corrupted, resulting in a state that was never present in the editor at any one time.

For example, sometimes some lines become truncated at the end in the editor.

Comment 1 Dani Megert

2010-12-15 11:11:52 EST

Please provide more info. For details see http://www.eclipse.org/eclipse/platform-text/development/bug-incomplte.htm.

Comment 2 Nicolas Bros

2010-12-15 11:39:13 EST

Created attachment 185242 [details]
configuration

This is with:
Eclipse SDK
Version: 3.7.0
Build id: I20101208-1300
JRE version : 1.6.0_22-b04

But I also noticed this problem a few times with older versions of Eclipse.

I have attached the complete configuration.

I cannot provide a simple way to reproduce, since the problem seems random, with a low frequency.

Do you need more information?

Comment 3 Dani Megert

2010-12-15 11:41:43 EST

>Do you need more information?
In which editor do you see this?

Anything in .log?

Comment 4 Nicolas Bros

2010-12-15 11:51:59 EST

(In reply to comment #3)
> In which editor do you see this?
In the Java editor (CompilationUnitEditor).

> Anything in .log?
no, nothing related

Comment 5 Dani Megert

2010-12-15 12:21:13 EST

I'm sorry but so far no luck to reproduce. Without steps or an error in the .log we can't do anything. Please reopen if you have more precise steps to reproduce.