My file got malformed. This is the second problem related to undo. Please take some
steps to remove them. Recent changes (optimizations) in undo are suspected. Using
current trunk version r21791 of jedit became risky.
I will try to reproduce, but had to paste the log and give a warning immediately.
8:18:49 AM \[main\] \[message\] Log: java.version=1.6.0_24
8:18:49 AM \[main\] \[message\] Log: java.vm.version=19.1-b02
8:18:49 AM \[main\] \[message\] Log: java.vm.name=Java HotSpot(TM) Client VM
8:18:49 AM \[main\] \[message\] Log: java.runtime.version=1.6.0_24-b07
8:18:49 AM \[main\] \[message\] Log: java.runtime.name=Java(TM) SE Runtime Environment
8:18:49 AM \[main\] \[message\] Log: java.vendor=Sun Microsystems Inc.
8:18:49 AM \[main\] \[message\] Log: java.compiler=null
8:18:49 AM \[main\] \[message\] Log: os.name=Linux
8:18:49 AM \[main\] \[message\] Log: os.version=2.6.32-5-686
8:18:49 AM \[main\] \[message\] Log: os.arch=i386
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: java.lang.AssertionError
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.buffer.UndoManager.getReplaceFromRemoveInsert(UndoManager.java:370)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.buffer.UndoManager.access$500(UndoManager.java:41)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.buffer.UndoManager$CompoundEdit.add(UndoManager.java:624)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.buffer.UndoManager.contentInserted(UndoManager.java:195)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.buffer.JEditBuffer.insert(JEditBuffer.java:736)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.buffer.JEditBuffer.insert(JEditBuffer.java:684)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.textarea.Selection$Range.setText(Selection.java:275)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.textarea.TextArea.replaceSelection(TextArea.java:2081)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.textarea.JEditTextArea.replaceSelection(JEditTextArea.java:248)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.Registers._paste(Registers.java:387)
11:13:37 AM \[AWT-EventQueue-0\] \[error\] BeanShellAction: at org.gjt.sp.jedit.Registers.paste(Registers.java:276)
Submitted | jarekczek - 2012-08-05 09:22:41 | Assigned | thomasmey |
---|---|---|---|
Priority | 5 | Labels | |
Status | pending | Group | None |
Resolution | fixed |
2012-08-09 15:47:14 k_satoda |
The failing assertion is:
|
---|---|
2012-08-09 20:24:42 jarekczek |
- **priority**: 8 --> 5 |
2012-08-09 20:24:42 jarekczek |
It was only once when I got it. I know I made a double paste, while usually I use "Duplicate lines" shortcut for that. I had several lines in clipboard. Probably previous activity plays role here. It was not a fresh instance of jedit, I did about hour of work before getting there. I know this is of little help, but that's all I can give at the moment. After all it's only an assertion, so maybe a usual priority of 5 would be enough. The other s&r ticket contains steps to reproduce. |
2012-08-10 09:21:54 thomasmey |
Mhh. I'll try to reproduce this one. But I guess this is an consecutive error of bug 3551910. |
2012-08-16 14:38:57 jarekczek |
After I got it again, despite the patch, I took a look at the code. Thank you for
detailed comments, they help a lot in such situations. I wonder if the writer had
in mind that this code will also be reached after regular edits and macros, not only
after search & replace. But that's a side note only.
|
2012-08-16 16:16:53 jarekczek |
And finally steps to reproduce:
|
2012-08-16 20:49:27 thomasmey |
"After I got it again, despite the patch, I took a look at the code. Thank
|
2012-08-16 20:50:40 thomasmey |
v1 Dont-compact-significant-Edits.patch (1.0Kio) |
2012-08-21 08:12:04 thomasmey |
"But there seems to be another bug with the dirty flag in your test case:"
|
2012-09-06 15:12:34 ezust |
- **assigned_to**: k_satoda --> thomasmey |
2012-09-06 15:13:19 ezust |
Committed 22171. |
2012-09-06 15:13:19 ezust |
- **status**: open --> pending-fixed |