Summary: | Step over is very slow and much slower than before | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Thomas Trost <fuerallesg> | ||||
Component: | Debug | Assignee: | Platform-Debug-Inbox <platform-debug-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | 2f.mail, ger_pyro, misc, reto.hoehener, sarika.sinha, solf.gm, v-poutissou, vkrevs | ||||
Version: | 4.8 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows 7 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Thomas Trost
2018-01-29 04:37:03 EST
The slowness may be a result of the "Show method result..." setting in Preferences > Java Debug. The reason is that for this feature "Method Exit Events" are observed, and that causes the JVM to disable the Just-In-Time compiler for the involved methods. In that case, you have to options: - Disable that setting - If no recursive invocations are involved, use "Run to Line" instead of "Step-Over" I have already disabled this setting. It improved the runtime a bit but still it is very slow as desribed. "Run to line" works fine comparable to "resume". Only "Step over" causes problems. can you try disabling "Advanced Source lookup" Preference under Java>Debug ? Still the same performance. I also suffer from this just about every day. For me the slowness is during stepping over a method that eventually calls SSLContext.getInstance("TLS"). Put a breakpoint immediately after the method that calls SSLContext.getInstance("TLS") and step over works reasonably quickly. Created attachment 275239 [details]
Project for slow debugging with oracle jdbc
Project for showing slow step over/into/return on method OracleDriver.connect()
Hi, Same trouble with Step Into/Step over/ Step return on OracleDriver().connect(...) (ojdbc8) It takes at least 45seconds to step over this method. If stopped at the line and then skipping all breakpoints (CTRL+ALT+B) or resuming, there's no performance issue. If stopped after the line, no performance issue. Not sure if you have Oracle databe, but here's a project for reproducing. It contains a main method calling new OracleDriver().connect(...) |