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

Bug 360003

Summary: UI freeze indefinitely while saving debugged file
Product: [Technology] DLTK Reporter: Kevin KIN-FOO <kkinfoo>
Component: Common-DebugAssignee: dltk.common-inbox <dltk.common-inbox>
Status: NEW --- QA Contact:
Severity: major    
Priority: P3 CC: kkinfoo
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Strack using kill -3 none

Description Kevin KIN-FOO CLA 2011-10-05 11:17:55 EDT
Created attachment 204606 [details]
Strack using kill -3

I'm developing upon Eclipse 3.6.2

% java -version
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.2) (6b22-1.10.2-0ubuntu1~11.04.1)
OpenJDK Server VM (build 20.0-b11, mixed mode)

I investigated and I may have found the problem.
After editing the file, auto build is lauched.
Auto build  detects resource modification and sends a notification.
This notification sends a "breakpoint_update" command through in ScriptDebugTarget#breakpointChanged.
The command is really sent in Dbgp DebuggingEngineCommunicator#communicate
Auto build acquired lock on workspace and waits for synchrone response to "breakpoint_update" command.
File save waits for auto build to release lock.
During this time IDE is frozen because save action is done in UI Thread.
Should not this command be sent separately in a Job or a Thread  ?
Comment 1 Kevin KIN-FOO CLA 2011-10-05 11:18:35 EDT
If you need more detailed trace just ask.
Comment 2 Kevin KIN-FOO CLA 2011-10-05 11:20:11 EDT
*** Bug 359957 has been marked as a duplicate of this bug. ***