On Wed, 8 Jan 2003, Thomas Dickey wrote:
> > The question is what happens when a memory leak is found ?
>
> While running, lynx keeps track of all of the allocated
> memory. On exit it walks through the list of chunks that
> were never freed and writes a report (Lynx.leaks) to the
> current directory. That's useful for some types of leaks -
> but some of the reallocations are done at a low-level by
> utility functions that don't give much context regarding
> where the real allocation was done. Besides keeping track,
> lynx also does a little more work to free up memory that
> would confuse the reporting (ncurses can be compiled to
> provide similar memory-freeing, for this purpose).
I don't know if it's related, but I was browsing with the new
build for a time and it apparently stopped at "HTTP/1.1 200 OK"
. I couldn't use ^Z. Then I noticed it was using all CPU. I had
to kill it. No Lynx.leaks. I'll try again.
--
0@pervalidus.{net, {dyndns.}org}
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
