Community
Participate
Working Groups
Build ID: M20071023-1652 Steps To Reproduce: 1.Startup Eclipse 3.3.1.1 on Leopard 2.Look in the system.log 3.see outdated options Then these are followed by lot of PermGen and out of memory errors More information: It shows: Nov 13 23:28:50 /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse[2469]: Unrecognized Java VM option ignored: -Xdock:icon=../Resources/Eclipse.icns Nov 13 23:28:50 /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse[2469]: Unrecognized Java VM option ignored: -XstartOnFirstThread Nov 13 23:28:56 /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse[2469]: CPSSetForegroundOperationState(): This call is deprecated and should not be called anymore.
See bug 209722 comment #5, the Xdock:icon, Xdock:name and XstartOnFirstThread are all vm args normally consumed by the java launcher and the eclipse launcher should consume them as well. This is not specific to leopard. I don't know about CPSSetForegroundOperationState, we do not make any calls to that function in the eclipse launcher.
(In reply to comment #1) > See bug 209722 comment #5, Which bug did you really mean? QuadBox:~ maarten$ java -X -Xmixed mixed mode execution (default) -Xint interpreted mode execution only -Xbootclasspath:<directories and zip/jar files separated by :> set search path for bootstrap classes and resources -Xbootclasspath/a:<directories and zip/jar files separated by :> append to end of bootstrap class path -Xbootclasspath/p:<directories and zip/jar files separated by :> prepend in front of bootstrap class path -Xnoclassgc disable class garbage collection -Xloggc:<file> log GC status to a file with time stamps -Xbatch disable background compilation -Xms<size> set initial Java heap size -Xmx<size> set maximum Java heap size -Xss<size> set java thread stack size -Xprof output cpu profiling data -Xfuture enable strictest checks, anticipating future default -Xrs reduce use of OS signals by Java/VM (see documentation) -Xdock:name=<application name> override default application name displayed in dock -Xdock:icon=<path to icon file> override default icon displayed in dock -Xcheck:jni perform additional checks for JNI functions -Xshare:off do not attempt to use shared class data -Xshare:auto use shared class data if possible (default) -Xshare:on require using shared class data, otherwise fail. The -X options are non-standard and subject to change without notice. No -XX though...
I meant bug 205990. Because we start the vm using the JNI invocation API, any options consumed by the java launcher are no longer getting consumsed and the vm itself may not recognize them.
Andrew, this fix needed for 3.4?
Will try and look at this post M6
not going to make M7
This will not make 3.4. There exists already a place to act on vm args and potentially filter some out, however this location would break the dock for restart/switch workspace. VM arguments are passed both to the VM and also to Eclipse itself (so that it can set the eclipse.vmargs property used for restart). These arguments would need to be filtered from the list passed to the vm but not the list passed to eclipse.
(In reply to comment #7) > This will not make 3.4. > > There exists already a place to act on vm args and potentially filter some out, > however this location would break the dock for restart/switch workspace. > > VM arguments are passed both to the VM and also to Eclipse itself (so that it > can set the eclipse.vmargs property used for restart). These arguments would > need to be filtered from the list passed to the vm but not the list passed to > eclipse. > This is still an issue. The system log continues to be filled with these messages. What you describe above sounds rather complicated. I would suggest deferring this bug out of 3.5.
This is still an issue in Galileo in all of carbon/cocoa and cocoa-64bit Apr 24 12:13:46 .../eclipse35M6-cocoa/Eclipse.app/Contents/MacOS/eclipse[46153]: Unrecognized Java VM option ignored: -Xdock:icon=../Resources/Eclipse.icns Apr 24 12:16:34 .../eclipse35M6-carbon/Eclipse.app/Contents/MacOS/eclipse[73209]: Unrecognized Java VM option ignored: -Xdock:icon=../Resources/Eclipse.icns Apr 24 12:24:57 .../eclipse35M6-carbon/Eclipse.app/Contents/MacOS/eclipse[58499]: Unrecognized Java VM option ignored: -Xdock:icon=../Resources/Eclipse.icns Maybe the Mac Developers can setup geektool from http://projects.tynsoe.org/en/geektool/ and use a shell script like this grep "Unrecognized Java VM option" /var/log/system.log to make these errors show up on the desktop Also handy to monitor lots of other logs...
We didn't end up having much time in 3.5 for launcher improvements, this did not make it.
*** Bug 286043 has been marked as a duplicate of this bug. ***
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.
