Article View: adobe.framemaker
Article #1144Re: Crash on saving file with fix but what was the cause?
From: Sheila_Carlisle
Date: Wed, 31 Dec 2008 05:30
Date: Wed, 31 Dec 2008 05:30
7 lines
1431 bytes
1431 bytes
Great sleuthing to narrow it down to a specific anchored frame! A few questions: What kind of content was in the anchored frames? was it for example a graphic copied into the frame, were there OLE (linked) objects, or was it a referenced graphic file, or ?? What setting do you have for File > Preferences "Save FrameImage with Imported Graphics"? Also, how much RAM do you have on your system? Do you often have other apps open when you work in FM, e.g. MS Office apps, or Photoshop or whatever? Years ago I recall having a problem with anchored frames seeming to cause crashes, it was as if FM was reaching some internal limit and at some point it just went "kablooie". I'm pretty certain that getting more RAM was the definitive solution in my case.
Technical Details
Message-ID:
<59b74b03.0@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!news2!feeder.erje.net!newsfeed.straub-nv.de!news.buerger.net!news4us.nl!webcrossingReferences:
<59b74b03.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,a8e7835e64cf7e25 X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Sheila_Carlisle@adobeforums.com Newsgroups: adobe.framemaker Subject: Re: Crash on saving file with fix but what was the cause? Message-ID: <59b74b03.0@webcrossing.la2eafNXanI> Date: Tue, 30 Dec 2008 21:30:18 -0800 References: <59b74b03.-1@webcrossing.la2eafNXanI> Lines: 16 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!news2!feeder.erje.net!newsfeed.straub-nv.de!news.buerger.net!news4us.nl!webcrossing