Re: [Colossus-developers] Trying to catch out of memory errors

[Clemens K. <lem...@sa...>]

> > > Log Message:
> > > -----------
> > > On Client side, catch the Out of memory error (and others) and display
> > an error dialog accordingly, so that the user knows that something is
> > seriously wrong... 
> > > and then rethrow it because all is lost anyway (going on would make
> > things only worse, as I noticed...)
> > 
> > Have you tested this?  Did the dialog actually pop up?

Besides: This catch clause does not only catch OOM error, but all kind
of JVM errors. Like serious IO errors and so on; so, now there will be 
a dialog so it becomes visible what (or at least THAT something) is wrong.
Not just: hangs, or "some expected thing" does not happen.

So, perhaps some of the open bugs (AI refuses to deploy..., or BattleMap does not open, ...) is some other weird runtime error and the user
just did not notice it because using webstart, (not knowing about JWS
console etc.)


BR,

Clemens


-- 
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser