- This topic has 6 replies, 2 voices, and was last updated 20 years ago by
.
-
Posts
-
I just upgraded to 3.8.3 from 3.8.2 on eclipse 3.01, linux GTK. Now every time I close the IDE, it locks up completely and I have to kill it by force. Can anyone help out?
christian
an additional observation: whenever the IDE *does* close (sometimes it works), I get 2 entries in the error log:
– a stack trace from the webbrowser plugin, which seems to check on shutdown whether the browser is operational (it is not, and I have unchecked the internal browser)
– an informational message simply stating “true/false”.rather discomforting, this. I am seeing the main tool for may daily work becoming even more unstable.
– a stack trace from the webbrowser plugin, which seems to check on shutdown whether the browser is operational (it is not, and I have unchecked the internal browser)
– an informational message simply stating “true/false”.Well, these actually have nothing to do with it. They’re common info outputs on all platforms.
When you upgraded, did you restart with -clean on the commandline? Does the behavior change after a clean reboot of your machines? What commandline options are you launching with?
>>Well, these actually have nothing to do with it. They’re common info outputs on all platforms.
I think it is rather bad habit to “pollute” the error log with useless messages. I am certainly not interested in this “info”, and who else would be looking at my log?>> When you upgraded, did you restart with -clean on the commandline?
no. what does the clean flag do?>>Does the behavior change after a clean reboot of your machines? What commandline options are you launching with?
what do you mean by a “clean reboot”? I am using only an additional -Xmx512m flagchristian
Christian,
I think it is rather bad habit to “pollute” the error log with useless messages. I am certainly not interested in this “info”, and who else would be looking at my log?
Your assumption that it’s an “error log” isn’t quite correct. It’s simply a “log” that contains selected output for platform and product developers (not end users). It is designed to contain whatever information we find useful, of all levels, info/warning/error. You’ll notice that Eclipse “pollutes” it with startup information everytime the workbench starts up. This is certainly not an an error output, simply information that plug-in developers find useful.
>> When you upgraded, did you restart with -clean on the commandline?
It basically forces Eclipse to rebuild the cache it contains of what plugins should be loaded at startup. It only needs to be done the first time after a large update, to ensure that the plugins from the last release are not included in the next startup and the new versions are picked up. Technically, it should not be necessary, but there have been several Eclipse bugs in managing the configuration cache. The bugs and rationale are additionally explained in our upgrade instructions here:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-5107.html
Suffice it to say, you should restart with -clean on the commandline after each upgrade to minimize any odd behaviors, possibly such as these.what do you mean by a “clean reboot”? I am using only an additional -Xmx512m flag
By “clean reboot” I simply meant a complete shutdown and restart of your Linux workstation. In addition to the -Xmx512m flag, we also recommend you use -Xms128M so that Eclipse starts with 128M available instead of the default 64M if you’re developing using a relatively large workspace or notice Eclipse pausing and swapping to grow the heap as you work.
ok, the lockup has ceased after I closed all files and then restarted the IDE. Sometimes eclipse’s behavior seems a little random..
Your assumption that it’s an “error log” isn’t quite correct. It’s simply a “log” that contains selected output for platform and product developers (not end users). It is designed to contain whatever information we find useful, of all levels, info/warning/error. You’ll notice that Eclipse “pollutes” it with startup information everytime the workbench starts up. This is certainly not an an error output, simply information that plug-in developers find useful.
my assumtion about the “error log” stems from the fact that the view has a title “Error Log”. Also, I cannot confirm that there is any startup information written to it. As far as I can tell everyone apart from myeclipse IS treating it as an error log.
I for my part always keep the error log view open to see if anything goes wrong (e.g., SQL error messages from the database explorer), and I find it annoying that I have to clean the log from meaingless messages every once in a while. In so far I also dont agree that the log is “not for end users” (assuming you call me an end user). In any case, its *my* log ;-), and I would appreciate if you could look into removing these messages.anyway, thanks for your help
christian
