[ggo-discussion] Re: gGo locks up when idle too long
- From: Peter Strempel <zotan@xxxxxx>
- To: ggo-discussion@xxxxxxxxxxxxx
- Date: Thu, 12 Dec 2002 17:01:43 +0100
On Thu, Dec 12, 2002 at 01:41:03PM +1300, <s.yeates@xxxxxxxxxxxxxxxx> wrote:
>
>
> > If I am away from my computer for a long time, and gGo isn't doing
> > anything, when I come back the program is frozen and any attempts to
> > get it to do anything result only in a 'ping' sound. The only way out
> > of this is to kill that instance of the java vm via task manager.
>
> I believe this the java locking resource contention bug showing
> itself. Try starting java with the extra command-line argument:
>
> -Djava.util.prefs.syncInterval=2000000
Stuart had already found this in the Java forums:
http://forum.java.sun.com/thread.jsp?forum=27&thread=231280
Have a look, at the page, it should explain what happens. This info was also
new for me.
I could add the fix to the gGo code, to avoid the extra commandline
argument. After all, poor windows users only double-click on an icon. :*)
Also not possible to give extra arguments if you use Webstart. So best
should be, I add this to my main() method in gGo.
Actually, I dont really understand this bug. The suggestion given on the
Java forum to make the Java systemprefs path world-writable sounds like a
horrible workaround.
Anyways, unless I add the fix to main(), you need to get Stuarts parameter
to the program start call somehow. Wont work with Webstart, so I fear you
need to wait for the next 0.3.2 preview and use this instead. I had not
gotten that problem myself yet, but I usually log out and close gGo instead
of going idle for longer.
Peter
Other related posts:
