Bugzilla – Full Text Bug Listing
| Summary: | Eclipse unresponsive when stepping through code (Linux) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mark Sutheran <mark> | ||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | arunkumar.thondapu, ericwill, mark, Michael_Rennie | ||||
| Version: | 4.3 | Keywords: | triaged | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 234585 [details]
Stack trace
Looks like the NPE in Caret (org.eclipse.swt.widgets.Caret.isFocusCaret(Caret.java:317))is the cause, moving to SWT for comment Any updates on this one? Happy to help if I can but need some pointers, and Eclipse is still completely unusable for debugging. Or perhaps suggestions for an alternate IDE that doesn't so exacerbate my homicidal tendencies on a daily basis? I have been trying to reproduce this issue using Eclipse 4.4 M2 running on Ubuntu 12.04 but I haven't been able to do it. Can you please download the 4.4 M2 build ( http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M2-201309182000/ ) and verify whether the same problem exists there too? Also, can you please try with a fresh workspace and check? The NPEs in the attached stack trace indicate that a disposed widget or display is being accessed but this shouldn't be happening. I suspect something is messed up either with the Eclipse installation or the workspace. Using a fresh Eclipse download and a new workspace should help confirm if that is the case. Thanks for the update Arun! So far (changing one thing at a time) I have been using the installation of 4.4 M2 build running on the existing workspace. At this point I have not see the same unresponsive behaviour. I will update the plugins to be identical to the broken version to see if one of them may be contributing. Thanks, Mark Can you still experience this bug with Neon? (In reply to Alexander Kurtakov from comment #7) > Can you still experience this bug with Neon? No response, closing this ticket. Please reopen it if the issue persists on GTK3.22 with 4.8. |
Description of the problem: Using JDT, and stepping through code while debugging, when Eclipse has to open a new Editor window to display the new source file it will often become completely unresponsive. The process has to be killed. Occasionally the following error appears instead: 'Debug Source Display' has encountered a problem An internal error has occurred (Widget is disposed) Similar behaviour can be observed when opening a window via the seach dialog - where a blank (grey) will sometimes appear instead of the normal editor. However in this case control is not lost it is usually possible to close the window and reopen via the navigator. Opening the source via the navigator does not appear to have problems. Steps to recreate: 1) Start debugging a java project - pause the debugger 2) Ensure that the editor windows for the source files are closed 3) Step through the stack, forcing Eclipse to open the new Editors for the source files automatically 4) Sooner rather than later the IDE becomes unresponsive The stack traces which appear to be related are attached. Details: System: Ubuntu 13.04 Installation: awt.toolkit=sun.awt.X11.XToolkit eclipse.application=org.eclipse.ui.ide.workbench eclipse.buildId=4.3.0.I20130605-2000