Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327985 - [typing] Using redo very fast sometimes fails and loses all stored redo information
Summary: [typing] Using redo very fast sometimes fails and loses all stored redo infor...
Status: CLOSED DUPLICATE of bug 319872
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-17 01:55 EDT by Art McBain CLA
Modified: 2010-10-18 02:26 EDT (History)
2 users (show)

See Also:


Attachments
Workspace log file (610.87 KB, text/plain)
2010-10-17 02:10 EDT, Art McBain CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Art McBain CLA 2010-10-17 01:55:06 EDT
Build Identifier: 20100617-1415

If you undo several times, then hold down the redo shortcut key (^Y), sometimes Eclipse will throw an IllegalWorkbenchException (or something similarly named). It then forgets all stored redo information past that point. This leaves the current document in an inconsistent state, wherever it died.

Hitting undo after causing this exception may result in another exception of the same, causing it to lose all undo information before that point.

Reproducible: Sometimes

Steps to Reproduce:
1. Make many edits to a document.
2. Undo many times to go back a ways.
3. Hold down the redo shortcut (^Y) to fast-forward to the most recent document state.
Comment 1 Art McBain CLA 2010-10-17 02:10:37 EDT
Created attachment 181045 [details]
Workspace log file

Log file from the workspace. Seems to be filled with stack traces that are all very similar and quite possibly all related to this bug. The log file appears to have been rotated, but this seemed more relevant than the older rotated out file.
Comment 2 Dani Megert CLA 2010-10-18 02:26:14 EDT

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