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

Bug 531988

Summary: Eclipse turns too slow and using 100% of CPU during debug
Product: [Eclipse Project] JDT Reporter: Girish Adat <girishadat>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: sarika.sinha
Version: 4.7.2   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X   
Whiteboard: stalebug
Attachments:
Description Flags
Configuration details. none

Description Girish Adat CLA 2018-03-04 23:32:48 EST
Created attachment 272991 [details]
Configuration details.

The Eclipse debugger becomes too slow, and the Mac's Activity Monitor showing 100 or just above 100% utilisation of CPU.  The problem goes away only after restarting Eclipse.

I could see that 3-4 times I had faced this problem. Note that I moved the breakpoints from Oxygen 1 to Oxygen 2 via export and import. It takes a few seconds (say 5-15 seconds) to highlight the first breakpoint, and similarly to move from one to next or next step.

As of now I am not facing the problem; but I will monitor eclipse via jvisualvm and add more details to fix this problem. Using the latest version as of now.

Version: Oxygen.2 Release (4.7.2)
Build id: 20171218-0600

Configuration attached.
Comment 1 Sarika Sinha CLA 2018-03-04 23:42:13 EST
Can you Go to
Preferences -> Java -> Debug and disable the option
"Show method result after a step operation (if supported by the VM; may be slow)".

And see if you are still facing the issue.
Comment 2 Eclipse Genie CLA 2020-04-25 17:01:55 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.