Community
Participate
Working Groups
N20050518 Investigating a bug, I pasted a stack trace into the stack trace console and followed a hyperlink. The busy cursor never went away. I produced two thread dumps showing the main thread wasy busy in JCORE code, and noticed the CPU was 50-100% busy and eventually memory got allocated to over 900MB. Went for coffee, and when I returned the process had terminated. Will attach thread dump and stack trace I was navigating.
Created attachment 21429 [details] thread dump
Could not reproduce after restarting workspace. The stack trace I was navigating was: org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.AbstractLineTracker.getLineInformation (AbstractLineTracker.java:251) at org.eclipse.jface.text.AbstractDocument.getLineInformation (AbstractDocument.java:832) at org.eclipse.debug.ui.actions.ToggleBreakpointAction.run (ToggleBreakpointAction.java:70) at org.eclipse.ui.texteditor.AbstractRulerActionDelegate.run (AbstractRulerActionDelegate.java:99) at org.eclipse.debug.ui.actions.RulerToggleBreakpointActionDelegate.runWithEvent (RulerToggleBreakpointActionDelegate.java:125) at org.eclipse.ui.internal.PluginAction.runWithEvent (PluginAction.java:236) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection (ActionContributionItem.java:538) at org.eclipse.jface.action.ActionContributionItem.access$2 (ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent (ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:842) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2901) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2534) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1601) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1565) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench (Workbench.java:315) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run (IDEApplication.java:103) at org.eclipse.core.internal.runtime.PlatformActivator$1.run (PlatformActivator.java:230) at org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:345) at org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:328) at org.eclipse.core.launcher.Main.basicRun(Main.java:272) at org.eclipse.core.launcher.Main.run(Main.java:974) at org.eclipse.core.launcher.Main.main(Main.java:950)
I noticed console hyperlink naviagation of stacktraces is extremely slow for large projects. I end up having to to a ctrl+shift+t to find the class then do a ctrl+l to goto line. But it should be faster to just click the hyperlink.
Did you get it lately? Some performance issues have been fixed regarding to the cache usage. Closing as REMIND. Please reopen if you get it again.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
