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

Bug 498390

Summary: Debugger behaves strange or crashes upon pressing CTRL + S (save)
Product: [Eclipse Project] JDT Reporter: Rik H. <rik.huijzer>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: rik.huijzer, sarika.sinha
Version: 4.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 10   
Whiteboard:

Description Rik H. CLA 2016-07-23 14:46:59 EDT 
While writing code in Eclipse my hand reaches out to CTRL + S quite often to get rid of false error information (to force refresh). I give two examples for when and why this is useful. Suppose one is in class B and updates the required input for a method without saving the class. If one then switches to class A and changes the input for the request for class B then Eclipse will falsely state that the input does not match any method. Second example. Suppose one is editing code. It sometimes happens that lines are corrected but the error lines (red) remain. 

The problem occurs when debugging. Since CTRL + S has become a reflex I sometimes press it in debugging mode. This most of the time results in strange behaviour (jumping to other lines without breakpoints) and occasionally lets the Java application crash.
Comment 1 Rik H. CLA 2016-08-12 14:20:39 EDT 
On second thought, problem seems puny. Closed issue.