In einer eMail vom Di, 27. Apr. 2004 16:26 MEZ schreibt "Niklas Bergh" <[EMAIL PROTECTED]>:
>> >> This behaviour ends normally >> >> in a Java VM crash after some time >> > >> >What do you mean with crash? >> > >> Look at the attachment, I attached some of the error messages of the past >months. They are called "HotSpot Virtual Machine Error" or something >similiar > >Urk, yes.. those are really crashed.. Unfortunately this is nothing that we >can do anything about.. it is a Sun-issue.. or a driver issue or a hardware >issue or something like that.. per definition this kind of crash should be >impossible to cause from a java application inside the JVM :( > >/N > Ok so I experience crashes which should never happen, nice :D I doubt that hardware problems are causing it, but I will make a little memory test to be sure that that is not the cause. The rest should be ok (It nearly never crashes and is running for a long time now, I just doubt damaged hardware ;) ), but a damaged memory would be logical in some way, because I got these crashes always when freenet allocated more then ~100MB (of a total of 256MB available). Thats why I have limited freenets memory usage to that now. I get these errors anyway, but at least I get them now only if freenet is (nearly) overloaded. I always thought that freenet would cause them, but ok, I will check the memory then. :| As soon as a new build with your logging improvements gets out I will report what is loged then, thanks for your help so far. :) _______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
