Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334460 - Eclipse 64 bit Hangs on Mac OS X with Java 1.6.0_22
Summary: Eclipse 64 bit Hangs on Mac OS X with Java 1.6.0_22
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.1   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2011-01-15 12:02 EST by Arpit Desai CLA
Modified: 2011-01-18 10:29 EST (History)
0 users

See Also:


Attachments
Thread Dump of Eclipse (31.56 KB, text/rtf)
2011-01-15 12:04 EST, Arpit Desai CLA
no flags Details
Error Log (40.65 KB, application/octet-stream)
2011-01-18 10:03 EST, Arpit Desai CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arpit Desai CLA 2011-01-15 12:02:22 EST
Build Identifier: I20100608-0911

I have installed Eclipse in 64 bit cocoa flavor and wiped it out nearly 6 times now andn every time I run into the same issue. Eclipse hangs up on me and starts throwing all sorts of errors at me about workspace and memory and builds. 

I then installed 32 bit version and it all works fine, although it is a bit slower than the 3.4 version I was using before. 

For further debugging I am attaching the thread dump here.

Reproducible: Always

Steps to Reproduce:
1. Install Eclipse Helios with 64 bit cocoa on Mac OS X
2. Open the workspace and get on with usual business of checking out SVN project and building it
3. Thats it it will hand
Comment 1 Arpit Desai CLA 2011-01-15 12:04:36 EST
Created attachment 186875 [details]
Thread Dump of Eclipse

Thread Dump when Eclipse was hung
Comment 2 Oleg Besedin CLA 2011-01-17 09:29:29 EST
(In reply to comment #0)
> ... Eclipse hangs up on me and
> starts throwing all sorts of errors at me about workspace and memory and
> builds. 

So, does it hang up or does it throw all sorts of errors?

The attached stack trace does not show a deadlock, rather the main thread reporting a error. What do the "all sorts of errors" say? Can you attach a log file with them?
Comment 3 Arpit Desai CLA 2011-01-18 10:03:58 EST
Created attachment 187004 [details]
Error Log
Comment 4 Oleg Besedin CLA 2011-01-18 10:29:30 EST
There are a bunch of out of memory errors in the log:

java.lang.OutOfMemoryError: Java heap space

The 64-bit VMs consume more memory, so it is quite possible that the default heap size works for your app in 32bit VM, but not 64bit VM. 

Also, depending on the application, VM, and OS some more involved arguments might help, such as "UseParallelGC" / "UseSerialGC".If simply increasing heap space does not help, do a search on those arguments on VM support forums.