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

Bug 290235

Summary:	[OLE] Problem with using OLE control and setting the max heap size
Product:	[Eclipse Project] Platform	Reporter:	baptiste <baptiste>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Felipe Heidrich <eclipse.felipe>
Severity:	normal
Priority:	P3	CC:	baptiste
Version:	3.5	Keywords:	triaged
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description baptiste

2009-09-23 06:27:58 EDT

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier: 20090619-0625

We have a program that uses the OLE support in SWT to display Windows Media Player inside our program. After many hours we found out that settings the max heap size of the JVM results in the OLE control to crash after some time.
If we don't set the max heap size the OLE control works absolutely fine, however as soon as we set a value for the max heap size it does not work again.
This issue has been seen on Windows 2000, XP and Vista

Reproducible: Always

Comment 1 Bogdan Gheorghe

2009-09-23 09:58:50 EDT

Which JVM are you using? Have you tried using other ones?

Comment 2 Leo Ufimtsev

2017-08-03 12:34:08 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

2020-03-12 15:33:38 EDT

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.