Bug 452387 - [platform] Unhandled event loop exception
Summary: [platform] Unhandled event loop exception
Status: CLOSED WORKSFORME
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2014-11-19 16:25 EST by EPP Error Reports CLA
Modified: 2019-11-24 14:54 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2014-11-19 16:25:17 EST
Hello committers,

we received a new error report for Eclipse 4.5.0.I20141029-2000.


General Information:
    anonymous-id:         93d7d963-868b-465f-b68e-ad5070ee3cda
    eclipse-build-id:     4.5.0.I20141029-2000
    eclipse-product:      org.eclipse.epp.package.committers.product
    operating system:     Linux 3.13.0 (x86_64) - gtk
    java-runtime-version: 1.7.0_65-b32

The following plug-ins were present on the execution stack (*):
    1. org.eclipse.core.databinding.observable_1.4.1.v20140910-2107
    2. org.eclipse.core.databinding_1.4.100.v20141002-1314
    3. org.eclipse.core.runtime_3.10.0.v20140724-1132
    4. org.eclipse.e4.ui.workbench_1.3.0.v20141024-2249
    5. org.eclipse.e4.ui.workbench.swt_0.12.100.v20141020-2115
    6. org.eclipse.equinox.app_1.3.200.v20130910-1609
    7. org.eclipse.equinox.launcher_1.3.0.v20140415-2008
    8. org.eclipse.swt_3.104.0.v20141029-1116
    9. org.eclipse.ui_3.107.0.v20141010-0853
    10. org.eclipse.ui.ide.application_1.0.600.v20141003-0522
    11. org.eclipse.ui.ide_3.10.100.v20141024-1629


Error Status:

    code:                   0
    plugin:                 org.eclipse.ui_3.107.0.v20141010-0853
    message:                Unhandled event loop exception
    fingerprint:            aa73ccdf
    exception class:        org.eclipse.swt.SWTException
    exception message:      Data does not have correct format for type
    number of children:     0
    
    org.eclipse.swt.SWTException: Data does not have correct format for type
    at org.eclipse.swt.dnd.DND.error(DND.java:287)
    at org.eclipse.swt.dnd.DND.error(DND.java:238)
    at org.eclipse.swt.dnd.FileTransfer.javaToNative(FileTransfer.java:70)
    at org.eclipse.swt.dnd.DragSource.dragGetData(DragSource.java:410)
    at org.eclipse.swt.dnd.DragSource.DragGetData(DragSource.java:227)
    at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(OS.java:-2)
    at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9137)
    at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
    at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(OS.java:-2)
    at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2482)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3411)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:638)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:582)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
   

    

Messages, stacktraces, and nested status objects may be shortened. Please visit 
http://dev.eclipse.org/recommenders/committers/confess/0.5/reports/-
for the complete error log.


Some general information and guidelines about how to use this bug report:

1. Feel free to move this bug to your own product and components. Please note
   that this bug is only accessible to Eclipse committers. If you move this bug
   please make sure that it's still in the "Security Advisor" group.

2. The bug contents of the fields status, resolution, keywords, and whitelist
   are presented to reporters. If you needs more information, please set the
   keyword "needinfo". This will trigger a specialized dialog asking the user
   to provide further details.

3. Use the following resolutions for the following situations:
   * CLOSED / FIXED: This bug has been fixed. Please provide additional
     information in the whiteboard field.
   * CLOSED / WORKSFORME: Use this resolution if you can't reproduce this issue
     and request further information. Please use the whiteboard text to specify
     more details what a user should provide and how.
   * CLOSED / INVALID: Use this resolution if the reported problem is a
     'user-configuration' problem. Please consider giving hints how to fix
     these issues in the whiteboard field.
   * CLOSED / NOT ECLIPSE: Use this if the problem is caused by another plugin
     not developed at Eclipse.org
   * CLOSED / MOVED: If this bug has been moved else where. Please provide more 
     information (e.g. a link) in the whiteboard field.

4. Please remember that only committers can view and comment on this bug. You
   may, however, manually add the reporting user to the bug's cc list. But keep
   in mind that the report may contains sensitive information.

5. If you are missing a feature, please file a enhancement request here:
   https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Recommenders.Incubator&component=Stacktraces
    
 

Thank you for your assistance.
Your friendly error-reports-inbox.


--
* Note: The list of present bundles and their respective versions was
  calculated by package naming heuristics. This may or may not reflect reality.
Comment 1 EPP Error Reports CLA 2014-11-19 16:25:18 EST
I've looked up the (to date) top-3 most similar bug groups and listed the 
closest bug of each group below. This report may or may not be duplicate of
those (low or similar scores for all entries may indicate that this hasn't
been reported yet):

>     1. Bug 449064: [m2e] Unhandled event loop exception – 0,5    
>     2. Bug 451318: [platform] Unhandled event loop exception – 0,5    
>     3. Bug 451587: [platform] Stand-In Stacktrace supplied by Eclipse Stacktraces & Error Reporting Tool – 0,5    


If this report actually is a duplicate of those, please mark it as such. This
information helps me to improve the recommendations further for the next issue.

Thank you for your assistance.
Your friendly error-reports-inbox.
Comment 2 Marcel Bruch CLA 2014-11-19 16:29:10 EST
What's the source and target of the DND?
Comment 3 Michael Vorburger CLA 2014-11-19 16:34:44 EST
Hi guys, my first use of error reporter.. not terribly useful, I fear.

This happens (reproducible-y) when I'm dragging a deleted file from Staged up to Unstage in EGit (it works when I right-click Remove from Index the deleted file).

Interestingly, EGit doesn't appear ANYWHERE above.. Not sure if that's a bug in Error Reporter, or because EGit somehow swallows an Exception?  I've therefore manually moved this to Product EGit myself - hope that's OK.

Also, I'm 99% sure, unless I'm too sleepy, that a minute ago I just typed something like above into the "Comment" box before submitting - shouldn't that comment be submitted as and be visible in this issue?
Comment 4 Marcel Bruch CLA 2014-11-19 16:45:07 EST
Thanks for the report!

(In reply to Michael Vorburger from comment #3)
> Also, I'm 99% sure, unless I'm too sleepy, that a minute ago I just typed
> something like above into the "Comment" box before submitting - shouldn't
> that comment be submitted as and be visible in this issue?

My bad. It's currently swallowed when creating a bug. A fix is in Gerrit and will be rolled out this weekend.
Comment 5 Thomas Wolf CLA 2019-11-24 14:54:11 EST
Very old EGit version. Not reproducible with current EGit. Closing as stale.