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

Bug 310996

Summary:

Debugger is painfully slow

Product:

[Eclipse Project] JDT

Reporter:

Johannes Rieken <johannes_rieken>

Component:

Debug

Assignee:

JDT-Debug-Inbox <jdt-debug-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

major

Priority:

CC:

darin.eclipse

Version:

3.6

Target Milestone:

---

Hardware:

Macintosh

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

stalebug

Attachments:

Description	Flags
movie showing a debug attempt	none

Description Johannes Rieken

2010-04-29 07:00:30 EDT

Build Identifier: 3.6M6

Populating the variables view and stepping takes easily a minute at full CPU utilization. 

Reproducible: Sometimes

Comment 1 Johannes Rieken

2010-04-29 08:32:09 EDT

Created attachment 166466 [details]
movie showing a debug attempt

Comment 2 Darin Wright

2010-04-29 14:50:40 EDT

It looks like you have your settings to display the 'toString()' as the label for all variables. Whem computing the toString for a value the debugger waits a maximum of 5 seconds for the toString() to complete. It looks like each "slow" variable takes about 5 seconds before failing...

If you switch "Preferences > Java > Debug > Detail Formatters" to "In the detail pane only", are things faster?

What sort of 'toString' do the slow/failing objects have? If they are expensive to compute, the debugger will be slow.

Comment 3 Johannes Rieken

2010-05-03 08:35:23 EDT

That helped. It's not really snappy, but it showed an noticeable improvement. Are there any other features you recommend not using due to performance penalties?

Comment 4 Johannes Rieken

2010-05-03 08:38:39 EDT

> What sort of 'toString' do the slow/failing objects have? If they are expensive
> to compute, the debugger will be slow.

It's mainly proxy objects (Java 'native' proxies).

Comment 5 Eclipse Genie

2018-10-26 17:56:12 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.

If you have further information on the current state of the bug, please add it. 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.