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:denn...@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


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.

Shmuel Wolfson

Reply via email to