Once you get any Errors (eg, OutOfMemoryError), the state of the JVM is in pretty bad shape, and you should just quit immediately and relaunch the app.
On 17/4/02 11:59 pm, "Graham Lea" <[EMAIL PROTECTED]> wrote: > I'm getting OutOfMemoryErrors in # 616 > After doing a search of the whole project for a simple string, anything I > tried to do, including pressing the Garbage Collection button, resulted in > an Out of Memory Error with no stack trace. > > Graham Lea > > -- > Software Engineer > Forge Research Pty Ltd > Suite 116, Bay 9, Locomotive Workshop > Australian Technology Park, Cornwallis Street > Eveleigh NSW 1430 Australia > Phone: +61 2 9209 4152 Fax: +61 2 9209 4172 > www.forge.com.au > > ---------------------------------------------------------------------- > This message contains privileged and confidential information intended > only for the use of the addressee named above. If you are not the > intended recipient of this message you must not disseminate, copy or > take any action in reliance on it. If you have received this message > in error please notify the sender immediately. Any views expressed in > this message are those of the individual sender, except where the > sender specifically states them to be the views of another (including > a Body Corporate). > ---------------------------------------------------------------------- > > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
