Summary: | Workbench freeze and crashes when run with the Apple Java 1.4.1 (final) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Christian LEMER <chris> | ||||||||||
Component: | UI | Assignee: | Andre Weinand <andre_weinand> | ||||||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||||||
Severity: | blocker | ||||||||||||
Priority: | P1 | CC: | andre_weinand, pwa, ulrich | ||||||||||
Version: | 2.1 | ||||||||||||
Target Milestone: | 2.1 RC3 | ||||||||||||
Hardware: | Macintosh | ||||||||||||
OS: | Mac OS X - Carbon (unsup.) | ||||||||||||
Whiteboard: | |||||||||||||
Attachments: |
|
Description
Christian LEMER
2003-03-12 09:44:25 EST
Andre, which VM do you use? Have you been able to get Eclipse running with this VM? I see that the bug report has been transferred to the platform-core... Maybe this is right or maybe my Summary was a little misleading.I just want to point out that the crash only appear when running a new workbench using VM 1.4.1 when I want to test new plugins that have been developed with 1.4.1 specific feature (like assert)In that case the "Main" application that appear when using the "Run as... Runtime Workbench" crashes.... just to be sure the bug is well described... it's a very very important issue for us! I'm on the IBM WebSphere conference right now, so my time to track the 1.4.1 final issues is somewhat limited. However, I've managed to download the 1.4.1. And I've found a workaraound for the problem that Eclipse started from the workspace under 1.4.1 would not activate and would crash after some mouseclicks. However, there seems to be a more severe issue with the 1.4.1 JVM which prevents me from rebuilding the workspace under 1.4.1. Anyway, I've attached a new MacOS X launcher. Please give it a try. Created attachment 4080 [details]
macosx launcher
I try with the new launcher and it seems to work for the different tests I've made. It's quite late in Belgium (00:30), so I could not go further but I'll install this version on 4 developer stations tomorrow (they are stuck with Java 1.4.1 anyway). A have still a question about Java 1.4.1 support and could not find any answer after browsing the site with quite an effort... We are very happy with the OS X version of eclipse (even if it was supposed to be only an Early Access version as described in the project plan 2.1). We would like to develop some eclipse plugins but using Java 1.4.1 specific features (i.e. assert). I notice that if I change the Java.JVMVersion in the Info.plist to 1.4.1 so that the eclipse application starts with Java 1.4.1, then it ends up with severe compilation problems (build failure with only big numbers as result). It's not really a big problem because I could run Eclipse in 1.3.1 and still compile and test using Java 1.4.1 (It's fixed now with the new mac laucher you send me). But it seems that the plugins developped that way could only run in an Eclipse configured with as Java.JVMVersion 1.4.1... So, before writing a bug report for this compilation issue, I would like to know if the Eclipse 2.1 for Mac OS X is supposed to be able to run with Java 1.4.1 as primary JVM... in other words, am I supposed to be able to run Plugins developed with Java 1.4.1 specific features? Many thanks for your time and for the very efficient solution to the bug! P.S.: I'm not very familiar with this bug report system... should I set the status to FIXED or should I wait the next IntegrationBuild, NightBuild or Release Candidate to do it? Yes, there is another severe bug #34658 that only shows up in the final version of Apple's 1.4.1 VM. A fix seems to have been found. fixed. Created attachment 4085 [details]
source code patch
fixed for RC3 *** Bug 34914 has been marked as a duplicate of this bug. *** Thanks for the patch Andre. Works great. *** Bug 34953 has been marked as a duplicate of this bug. *** Approved for RC3 by Erich and Andre Created attachment 4129 [details]
the fix
Created attachment 4130 [details]
a better fix
Fix reviewed by EG released for I20030314 chris, can you verify that this bug is fixed ? Thanks a lot! [Chris, just add the comment "Verified for RC3" and check "Mark bug as Verified"] |