266575 – 64-bit Cocoa SWT bound by 256MB heap limit

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

Bug 266575 - 64-bit Cocoa SWT bound by 256MB heap limit

Summary: 64-bit Cocoa SWT bound by 256MB heap limit

Status:	RESOLVED DUPLICATE of bug 265525

Alias:	None

Product:	Equinox
Classification:	Eclipse Project
Component:	Framework (show other bugs)
Version:	3.5
Hardware:	Macintosh Mac OS X

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	equinox.framework-inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2009-02-27 18:50 EST by Scott Kovatch
Modified:	2009-03-04 11:39 EST (History)
CC List:	5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Scott Kovatch

2009-02-27 18:50:04 EST

From Mike Swingler:

* x86_64 is unusable without bumping up the heap size to at least 
512m. Everything about my workspace crashes (auto completion, 
background compilation, etc), and the app won't even quit properly 
unless I raise the heap.

This makes sense, as a 64-bit app will need more memory off the bat. However, the standard Eclipse.app sets -Xmx256m in eclipse.ini, which seems like an arbitrary cutoff point. It's definitely inadequate for a 64-bit app, and furthermore, it looks like the Mac is the only platform where this is set, looking through org.eclipse.equinox.

Is there some reason this was set in the first place?

Comment 1 Scott Kovatch

2009-02-27 18:52:43 EST

Probably belongs in Equinox, not SWT.

Comment 2 Thomas Watson

2009-03-02 15:58:35 EST

The other eclipse.ini files for the other platforms are in the org.eclipse.platform-feature project.  I'm not certain why the only the MAC ones are included in org.eclipse.equinox.executable project.  If this is needed for x86_64 Cocoa then it likely needs to be done for x86_64 win32.

Comment 3 Thomas Watson

2009-03-04 11:39:56 EST


*** This bug has been marked as a duplicate of bug 265525 ***