FM abruptly closes with no save

[Diane Gaskill]

Hi Framers,

I run FM8.02 on a laptop running XPSP2 with 2GB of RAM.  I have recently
experienced several crashes in situations that I never had crashes with when
using FM7.0.  Sometimes it saves and I get a recovery file, but most of the
time it does not save, it just halts and the FM window closes.  When it
comes back up, it acts like nothing happened.  No error messages, no
nothing.  Business as usual.  Wot, who me?

I know that Adobe people do monitor this list (and have for many years) so I
need to ask - what is the best way to report this? I have a couple of dumps
I can send.

I'd also suggest to the other FM users on the list who have posted about
their crashes, that they report their crashes too.  Posting them on the list
is good and maybe someone knows a workaround for some situations, but the
more Adobe has to work with, the better chance they have of finding the bug
and fixing it.  It sounds like a bug to me.

Diane Gaskill
(former tech support engineer)
=================================


-----Original Message-----
From: framers-bounces at lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com]On Behalf Of Brewster,
Christopher C
Sent: Thursday, February 14, 2008 8:08 AM
To: framers at lists.frameusers.com
Subject: RE: FM abruptly closes with no save


I think the memory issue is indeed the cause for this. I did my process
again and saved after each insertion. No problems occurred. But I think
software should handle a memory issue much more gracefully than simply
closing without saving-such as warning me, or refusing to execute the
step that would make it close. (Do Adobe people monitor this list?)



________________________________

From: Dennis Brunnenmeyer [mailto:dennisb at kvmr.org]
Sent: Wednesday, February 13, 2008 8:50 PM
To: Shmuel Wolfson
Cc: Brewster, Christopher C; framers at lists.frameusers.com
Subject: Re: FM abruptly closes with no save



Hi...

No one in this thread has mentioned that, when working with graphics,
FrameMaker likes to have plenty of RAM available to it, especially if
other applications are open and also have images loaded. There's no
"rule of thumb" that I know of, but I wouldn't attempt to do much with
multiple graphic files unless I had at least 1GB or preferably 2GB or
more of RAM on my system. 512MB or less is an invitation to a crash.

Dennis Brunnenmeyer
eMail:  dennisb /at/ chronometrics /dot/ com

**********************************************

At 09:14 AM 2/13/2008, Shmuel Wolfson wrote:



I've had it close when scrolling a document that has embedded Corel
graphics, when I scrolled too fast and did not wait for the embedded
graphics to appear.


Regards,
Shmuel Wolfson
052-763-7133





_______________________________________________


You are currently subscribed to Framers as dgcaller at earthlink.net.

Send list messages to framers at lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscribe at lists.frameusers.com
or visit
http://lists.frameusers.com/mailman/options/framers/dgcaller%40earthlink.net

Send administrative questions to listadmin at frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.