Bug 567422 - [Win32][DND] Drag and Drop can crash if target keep
reference to COM object

The aggressive release of all COM objects after the drag/drop
operation is done can be problematic if the drop target keeps a
reference to one of the COM objects for later use. When the target later
tries to release (or access) the already disposed COM object a crash
from invalid memory access is likely.

Instead if should trust that the target will eventually release the
references it still holds.

For the case that the target will request the data again after DND is
finished the last requested data is cached. Note: sending a DragSetData
event before DragStart or after DragEnd is considered a bug.

Change-Id: I48e88a58e46111a3879e071d56abb79ac75114a9
Signed-off-by: Paul Pazderski <paul-eclipse@ppazderski.de>
2 files changed
tree: 9a52a548f6817361130441e145d4a8a6c46fdefa
  1. .gitignore
  2. CONTRIBUTING
  3. LICENSE
  4. NOTICE
  5. README.md
  6. bundles/
  7. container/
  8. examples/
  9. features/
  10. local-build/
  11. pom.xml
  12. tests/
README.md

Contributing to SWT

Thanks for your interest in this project.

Developer resources:

See the following description for how to contribute a feature or a bug fix to SWT.

Information regarding source code management, builds, coding standards, and more and be found under the following link.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Contact:

Contact the project developers via the project's “dev” list.

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!