Date:	Sun, 14 Feb 1999 13:10:11 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Daniel Barker <sokal AT holyrood DOT ed DOT ac DOT uk>
cc:	djgpp AT delorie DOT com
Subject:	Re: EMACS and/or Windows 98 crash
In-Reply-To:	<Pine.GSO.3.95.990213051250.15150B-100000@holyrood.ed.ac.uk>
Message-ID:	<Pine.SUN.3.91.990214130947.15332G-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Sat, 13 Feb 1999, Daniel Barker wrote:

> The crash was on exiting DJGPP EMACS 19.34, from FILES menu / Exit
> Emacs.

Did Emacs itself print the DJGPP crash traceback?  If so, please post
it.

I sometimes get problems like that when, during the Emacs windowed
session, I suspend Emacs (with `C-z' or `C-x C-z').  Did you do that?

If you did, my solution is not to suspend Emacs when it runs on
Windows.  You don't need that, anyway (just open another DOS box
instead).  I think the problem is connected to the code where Emacs
restores the contents of the display before it exits, but my attempts
to debug this problem were unsuccessful.

I also don't exit Emacs on Windows.  It is fired up on start-up and
runs all the time until shut-down.  Why did you need to exit?

> I asusme due to some resource leak, the computer
> typically gets slower and slower, becoming almost unbearable after about a
> week without re-boot.

I'm not sure this has anything to do with the crash.  All the data you
posted points to display-related problems (``Combined VGA/DIB 386
enhanced mode display component attempted to access memory that does
not exist.'').

But if you suspect Emacs is leaking memory, please use some tool that
reports memory used by DOS programs, and post the data.

- Raw text -