Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 392860 - Pressing ctrl+q while the mini "Editors" list window is active causes instant crash
Summary: Pressing ctrl+q while the mini "Editors" list window is active causes instant...
Status: CLOSED DUPLICATE of bug 411602
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.2.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-25 14:53 EDT by Andrew Arace CLA
Modified: 2014-06-13 10:28 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Arace CLA 2012-10-25 14:53:57 EDT
Windows 7, base install of Juno SR1 64bit, new workspace, new simple Java project, requires at least a single java editor (.java file) window open.
(The default key combination for "Next Editor" is ctrl+F6, changing this default binding to something else does not change the bug. I initially discovered this because I had changed my "Next Editor" shortcut to be ctrl+tab, and "q" is next to tab)

If you press ctrl+f6, and while still holding in ctrl, and the small window titled "Editors" is open in the center of the screen, pressing the letter "Q" causes eclipse to close/crash immediately.
This happens even if the .java file has been edited and unsaved. Changes to unsaved files and changes to the workspace are lost.

No log files or dump files are created, that I could find.
This is easily reproducible.
Comment 1 Paul Webster CLA 2012-10-25 15:26:53 EDT
Caused by this entry in the LegacyIDE.e4xmi:

    <bindings xmi:id="_UW9TZfr3Ed6gmo7caOxU9g" elementId="_UW9TZfr3Ed6gmo7caOxU9g" keySequence="CTRL+Q" command="e4.exit"/>


PW
Comment 2 Benjamin Brandl CLA 2014-05-30 07:40:40 EDT
Propably duplicate of Bug 411602
Comment 3 Paul Webster CLA 2014-06-13 10:28:21 EDT

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