[Coco] Network Access for my COCO

[Aaron Wolfe]

With such vague details I can only guess, but the default memory limit
for Java programs is rather small on some operating systems (8 or 16MB
total).  DW can operate in these conditions, but if you leave the GUI
open and have logging turned on it will eventually run out of room.
At that point it halts logging and anything else that it can (the
message you mentioned) in an attempt to keep services alive to the
coco, but it can only do so much.

If your memory limit is small, try increasing it. If you have detailed
logging enabled, trying turning it off.  You can also close the GUI
when you don't need it instead of leaving it open all the time, that
way you can leave logging detailed etc.



On Mon, Jan 6, 2014 at 6:00 PM,  <billg999 at cs.uofs.edu> wrote:
>
>
> So, results of my first 48 hours of DriveWire4.
>
> It worked pretty god for a bit over 24 hours.  Then at some point
> it died, completely.  The COCO crashed and the DW Console had a
> message about stopping loggin because it was low on memory. Hmmm.
> Sounds like a serious memoryleak.  Maybe I need to go back to one
> of the earlier releases and see if it is different.
>
> Anybody else using telnet sessions into their COCO and seeing strange
> behaviour?
>
> bill
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco