Bugzilla – Full Text Bug Listing
| Summary: | udc dialog keeps coming up | ||
|---|---|---|---|
| Product: | [Technology] EPP | Reporter: | arne anka <eclipse-bugs> |
| Component: | Usage Data Collector | Assignee: | Wayne Beaton <wayne.beaton> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P2 | CC: | cgold, eriklovlie, mknauer, remy.suen |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | 1.3.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
arne anka
Can you provide some more information - What version of Eclipse are you using? What were you doing when this dialog came up? What is a "udc" dialog? - version? what part of the automatically included information did you miss? - the dialog pops up after starting eclipse - "udc" seems to mean "usage data collector" -- the acronym is coined and used by eclipse itself Reassigning to EPP FWIW, Chris has probably never actually seen the UDC. UDC is created by a different project and is added as part of the package creation process. Chris works on the Platform project and so likely never downloads things like Eclipse IDE for Java developers. Anyway... Can I assume that you are highlighting the "Turn the UDC feature off" radio button and clicking "Finish"? Are there any messages being generated in the [workspace]/.metadata/.log ? i though there would be a nomenclature, to be checked if reports contain terms and acronyms not familiar? "Can I assume that you are highlighting the "Turn the UDC feature off" radio button and clicking "Finish"?" exactly. as for the log: nothing related (neither by content nor by timestamp). In the preferences dialog, on the "Usage Data Collector" page, is the "Enable Capture" checkbox checked? If yes, does unchecking it help? I really want to get this sorted out, but I also want to get you past this problem... Try turning off the UDC all together by opening the Preferences, navigating to "General > Startup and Shutdown", and turning off both the "Usage Data Gathering Plug-in" and "Usage Data Recording Plug-in" entries. This should keep the UDC off (until you open the preferences page which would force it active). The obvious work around is to remove the feature. However, we haven't yet provided that functionality (I believe we have a bug open for that). The "Eclipse Classic" download does not include the UDC if you want to go that route. Thus far, I have not been able to replicate the bug myself. I will continue to try. I received an email from another user complaining of similar symptoms. I've looked through the code and am still not sure how this is happening. There is clearly a corner case that I'm missing. A theory: the UDC starts by gathering events for five days. After that period of time, it presents the user with the upload dialog, at which point the user can decide to "turn off the UDC". The data collected to that point is retained in a directory on the user's workstation. Henceforth, the UsageDataService itself will be turned off which stops any further data gathering. However, the process that monitors the data gathering service (UsageDataRecorder) remains on. The theory at the time was that the "recorder" process won't do anything if the "gathering" process is not turned on and generating events that "poke" the recorder. There are no obvious other entry points to kick off the upload process. We are well passed the time to redesign how the UDC starts up. Frankly, it's pretty convoluted at this point, and we do end up creating a handful of objects whether the UDC is turned on or not. We have several reuse scenarios that need to be considered. Perhaps by retooling the start up we may uncover the source of this bug. I'd like to know the source so that we can devise a test to ensure it doesn't reoccur. If this has not been resolved prior to our next release, I will add a check for isEnabled() in the UsageDataRecordingSettings#isTimeToUpload() method. It's never time to upload when the UDC is disabled. I realize this bug is old, but this is still happening. Quite annoying actually, as the dialog popped up and took the keyboard focus. Error log (can̈́'t see anything relevant here): !SESSION 2011-12-16 20:38:38.878 ----------------------------------------------- eclipse.buildId=M20110909-1335 java.version=1.6.0_23 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product !ENTRY org.eclipse.core.resources 2 10035 2011-12-16 20:38:42.374 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.ui.workbench 2 0 2011-12-16 20:45:42.494 !MESSAGE A handler conflict occurred. This may disable some commands. !SUBENTRY 1 org.eclipse.ui.workbench 2 0 2011-12-16 20:45:42.494 !MESSAGE Conflict for 'org.eclipse.ltk.ui.refactor.create.refactoring.script': HandlerActivation(commandId=org.eclipse.ltk.ui.refactor.create.refactoring.script, handler=ActionDelegateHandlerProxy(null,org.eclipse.ltk.ui.refactoring.actions.CreateRefactoringScriptAction), expression=AndExpression(ActionSetExpression(org.eclipse.cdt.ui.CodingActionSet,org.eclipse.ui.internal.WorkbenchWindow@3219ee8a),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@3219ee8a)),sourcePriority=16640) HandlerActivation(commandId=org.eclipse.ltk.ui.refactor.create.refactoring.script, handler=ActionDelegateHandlerProxy(null,org.eclipse.jdt.internal.ui.refactoring.actions.CreateRefactoringScriptAction), expression=AndExpression(ActionSetExpression(org.eclipse.jdt.ui.CodingActionSet,org.eclipse.ui.internal.WorkbenchWindow@3219ee8a),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@3219ee8a)),sourcePriority=16640) !SUBENTRY 1 org.eclipse.ui.workbench 2 0 2011-12-16 20:45:42.494 !MESSAGE Conflict for 'org.eclipse.ltk.ui.refactor.show.refactoring.history': HandlerActivation(commandId=org.eclipse.ltk.ui.refactor.show.refactoring.history, handler=ActionDelegateHandlerProxy(null,org.eclipse.ltk.ui.refactoring.actions.ShowRefactoringHistoryAction), expression=AndExpression(ActionSetExpression(org.eclipse.cdt.ui.CodingActionSet,org.eclipse.ui.internal.WorkbenchWindow@3219ee8a),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@3219ee8a)),sourcePriority=16640) HandlerActivation(commandId=org.eclipse.ltk.ui.refactor.show.refactoring.history, handler=ActionDelegateHandlerProxy(null,org.eclipse.jdt.internal.ui.refactoring.actions.ShowRefactoringHistoryAction), expression=AndExpression(ActionSetExpression(org.eclipse.jdt.ui.CodingActionSet,org.eclipse.ui.internal.WorkbenchWindow@3219ee8a),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@3219ee8a)),sourcePriority=16640) !SUBENTRY 1 org.eclipse.ui.workbench 2 0 2011-12-16 20:45:42.494 !MESSAGE Conflict for 'org.eclipse.ltk.ui.refactor.apply.refactoring.script': HandlerActivation(commandId=org.eclipse.ltk.ui.refactor.apply.refactoring.script, handler=ActionDelegateHandlerProxy(null,org.eclipse.jdt.internal.ui.refactoring.actions.ApplyRefactoringScriptAction), expression=AndExpression(ActionSetExpression(org.eclipse.jdt.ui.CodingActionSet,org.eclipse.ui.internal.WorkbenchWindow@3219ee8a),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@3219ee8a)),sourcePriority=16640) HandlerActivation(commandId=org.eclipse.ltk.ui.refactor.apply.refactoring.script, handler=ActionDelegateHandlerProxy(null,org.eclipse.ltk.ui.refactoring.actions.ApplyRefactoringScriptAction), expression=AndExpression(ActionSetExpression(org.eclipse.cdt.ui.CodingActionSet,org.eclipse.ui.internal.WorkbenchWindow@3219ee8a),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@3219ee8a)),sourcePriority=16640) FWIW, the UDC has been removed from the next version of all packages. We're shutting down collection. (In reply to comment #8) > I realize this bug is old, but this is still happening. Quite annoying > actually, as the dialog popped up and took the keyboard focus. There doesn't appear to be anything useful in the log. Have you tried just turning the UDC off completely? (From comment #6) > Try turning off the UDC all together by opening the Preferences, navigating to > "General > Startup and Shutdown", and turning off both the "Usage Data > Gathering Plug-in" and "Usage Data Recording Plug-in" entries. This should keep > the UDC off (until you open the preferences page which would force it active). |