Comment 16 for bug 68020

I should add that my earlier comment was wrong to advise running under GCJ as a workaround - this will indeed fix the problem with crashing on startup when there is an informational message to be displayed (without having to delete the logs), but as some people are reporting Azureus then crashes randomly after that. These random crashes do not/have never happened with Sun Java, so I'm not sure if Christian's comment is relevant - unless you are also saying that it can now show informational messages on startup under your configuration? I wouldn't know as I haven't kept up-to-date recently.