Bugzilla – Full Text Bug Listing
| Summary: | Use of IProgressService causes WARNING java.lang.RuntimeException: WARNING: Prevented recursive attempt to activate part | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | vikas <vikasholkar> |
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | prakash, remy.suen |
| Version: | 3.3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
vikas
(In reply to comment #0) > Build Identifier: Target platform 3.3.2 Does this happen with a 3.6 target platform? On what grounds is this a bug of "critical" severity? Does this happen with a 3.6 target platform? Thanks for quick response. According to our application requirement we have modified org.eclipse.workbench 3.3.1 plugin. Due to this we need to use 3.3.2 as target platform. On what grounds is this a bug of "critical" severity? It logs a Warning related to prevented recursive attempt to activate part and also create Unhandled Event loop exceptions. Regards, Vikas (In reply to comment #2) > Does this happen with a 3.6 target platform? > > Thanks for quick response. > According to our application requirement we have modified org.eclipse.workbench > 3.3.1 plugin. Due to this we need to use 3.3.2 as target platform. This doesn't actually answer my question. :o The 3.3.x line is no longer under maintenance. We need verification on whether this is still a problem on 3.6. The fact that you have locally modified org.eclipse.ui.workbench also presents an additional variable in this matter. Please provide code/reproducible steps which shows the problem on Eclipse 3.6 or one of our integration builds. http://download.eclipse.org/eclipse/downloads/ > On what grounds is this a bug of "critical" severity? > > It logs a Warning related to prevented recursive attempt to activate part and > also create Unhandled Event loop exceptions. What is the stack trace of the event loop exception? Is it constantly appearing? Does the workbench become unusable? In addition to Remy's questions: org.eclipse.ui.internal.presentations.r33.DefaultTabFolder$1.closeButtonPressed(DefaultTabFolder.java:66) at org.eclipse.ui.internal.presentations.r33.PaneFolder.notifyCloseListeners(PaneFolder.java:601) at org.eclipse.ui.internal.presentations.r33.PaneFolder$3.close(PaneFolder.java:190) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2171) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:324) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) The stack trace indicates that you have pressed the close button with your mouse. Is that the case? Hi We did not tested myApp on Target platform 3.6. The stack trace is observed when i click on Close button on com.myApp.SampleView. Following is stack trace for Unhandled Event loop Exception which is observed alongwith WARNING. The workbench is usable after this exception and WARNING message. org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:3777) at org.eclipse.swt.SWT.error(SWT.java:3695) at org.eclipse.swt.SWT.error(SWT.java:3666) at org.eclipse.swt.widgets.Widget.error(Widget.java:446) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:384) at org.eclipse.swt.widgets.Widget.getData(Widget.java:500) at org.eclipse.ui.presentations.PresentationUtil$4.handleEvent(PresentationUtil.java:81) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at com.myApp.core.Application.run(Application.java:55) 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:597) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethod(EclipseAppContainer.java:572) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:171) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) at org.eclipse.equinox.launcher.Main.main(Main.java:1148) "We observed that avoiding progress service with busy cursor from com.myApp.part view, the warning is not observed. However we need busy cursor to indicate progress small time events." If all you need is a busy cursor, why can't you use BusyIndicator.showWhile()? Hi Prakash, Thanks for reply. "If all you need is a busy cursor, why can't you use BusyIndicator.showWhile()?" 1. We require functionality to "Cancel" the long running tasks. Due to this we are using progress service with busyCursorWhile so that monitor dialog is displayed if selection is taking long time and for short time we do not see any dialog box. 2. I tried using BusyIndicator.showWhile() and it works well. But for long running tasks, it does not provide functinality to cancel the running task. 3.3 is out of support. We cannot fix this unless we can reproduce it in 3.6. Please try with 3.6 and let us know the steps to reproduce this. Please reopen if you can reproduce this on 3.6 |