Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 43037

Summary:	[OLE] Variant not disposed in OleEventSink
Product:	[Eclipse Project] Platform	Reporter:	Avneesh Saxena <as2uv>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Felipe Heidrich <eclipse.felipe>
Severity:	normal
Priority:	P3	CC:	snorthov, veronika_irvine
Version:	3.0	Keywords:	triaged
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Avneesh Saxena

2003-09-12 14:04:02 EDT

In the implementation of
OleEventSink class, its invoke() method constructs a new Variant, that
in turn, increments the refCount of the interface (if it is wrapping such).
However, the function never releases the reference as the variant is not
disposed ever. Veronika mentioned that currently the listeners have to 
explicitly free up the variant. However, the problem arises when multiple 
listeners are registered
with the Event sink. Whose responsibility is it to dispose of the Variant? I
don't think that the order of event dispatch can be relied on. How about the
event sink freeing up the Variant and all the users of the variant
should explicitly call AddRef() if they want to hold on to the IDispatch.

Comment 1 Felipe Heidrich

2009-08-12 12:52:53 EDT

Your bug has been moved to triage, visit http://www.eclipse.org/swt/triage.php for more info.

Comment 2 Leo Ufimtsev

2017-08-03 12:32:04 EDT

This is a one-off bulk update. (The last one in the triage migration).

Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process:
https://wiki.eclipse.org/SWT/Devel/Triage

See Bug 518478 for details.

Tag for notification/mail filters:
@TriageBulkUpdate

Comment 3 Eclipse Genie

2019-12-11 12:27:45 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.