Re: lynx-dev memory Exhausted

[Patrick Ash]

I have had this happen a few times now. usually it is after 3-4
weeks, I have not really kept  close track of it. Not a major
problem, but just an inconvenience sometimes, especially if it
happens when I am looking at something important. 

Pat


 Mon, 22 Jul 2002 18:16:30 -0700 (PDT), Matt Ackeret wrote:
>>
>>memory exhausted. Data transfer interrupted.
>>
>>I normally leave lynx running in the background all the time, so I
>>assume that some virtual address space or cache limit has been
>>exceeded. The only way to get rid of the problem is to quit from lynx
>>and restart.
>
>How long are you leaving lynx running at a time?
>
>Maybe there's a memory leak in lynx, or over-agressive caching of
>some kind?

-- 
Patrick Ash 
address@hidden

This OS/2 system uptime is 1 day, 12:23 hours and 44 seconds


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden