Re: SeaMonkey 2.35b7

Dave Yeo wrote:

> I use EPM sometimes. It also has a habit of crashing occasionally,
> perhaps due to memory problems. I like it but it is a line editor so
> somewhat weird.

Since I've discovered "System Load: DosQuerySysInfo()" as my needed
live monitor for shared and private memory, I'm experimenting a bit
more agian.

About EPM: I see often crashes in etke603.dll, with an entry in
popuplog.os2. Often, because I test a lot, also not very usual
situations. Since yesterday, I know that it always happens when the
lower shared mem is 0 MB.

I tried with highmem.exe to load the data of etke603.dll high. Then
EPM won't start anymore. But loading only its code high works well.
Not much won, but at least a new DLL that allows for loading to
higher shared memory. Since etke603.dll is responsible for the main
part, the edit control, loading its dat high should probably have
cured that problem.

Sinnce yesterday, I'm able to load a bit more than 60 MB files in EPM,
before that it was only 52. It doesn't matter how many files are loaded,
just the sum counts. Closing a file won't release that memory, at least
not until all EPM processes are closed. But I'm also experimenting with
VIRTUALADDRESSLIMIT at the same time.

> Seems there should be lots of editors floating around as it is a
> usual practice program.

We need a text eitor that is able to load large files partly. VSlick is
an example, MED and, IIRC, JEdit are not.

About Mozilla and strange shared memory behavior: I notice that
closing a recent Mozilla (I use SeaMonkey 2.35) won't release all lower
shared memory that was available before on close. It works only well
for the higher shared memory.

I've loaded several DLLs high, among them is /b xul.dll.

-- 
Andreas Schnellbacher