FrameMaker 8 crashing constantly

I am about to post a message with more details of FM 8 crashes (PDF and Book Update/Generate). Larry Carey mentioned something about a "I can produce PDFs fine (with the highly publicized "fix"). What fix is that?

Does anyone know if Save As PDF is related to issues with Book Update/Generate?

Ken Whitaker
Seattle, WA

This post seems to reflect my experiences with FrameMaker 8 on Vista.

I downloaded Frame 8 to create a Christmas & New Years newsletter. The graphics are in JPEG, PNG, PSD,and one GIF. I have 12 pictures on two pages. The computer is a Dell 1520 laptop, Vista, 128 MB video card, 2 GB RAM, 200 GB 7200 RPM drive. Have been using FrameMaker for 12 years.

I experienced four or more crashes a day. The FrameMaker application freezes and the window whittens. This seems to happen when I cut and paste. If I hold the mouse button down too long also might cause it.

I really can't figure out what the problems is. The Adobe InDesign version of my previous newsletter was essentially the same letter. InDesign on Vista does not crash; FrameMaker 8 on Vista crashes often.

Hi Larry,
I would like to help you with these crashes. Can you send me some of the crash logs at sgoyal@adobe.com.
Thanks,
--Sumeer

Hi Mike,

I have updated the drivers and performed the Windows OneLive Care analysis and recommended fixes. Video drivers/acceleration - have the latest with Acceleration set to Full.

Bad Fonts.... Upon opening some templates I have created with Frame 5.5 and 6.0, I did receive different Font Messages which as I remember were advisories stating a font did not exist and Frame 8. was going to substitue X for X. Although, I did not receive these messages when creating the new templates in FM 8. How does one check for bad Fonts?

Directory Errors - Have not had any issues with any directory issues. With the system maintenance checks I have performed I think (hope) any existing errors would have been found and corrected. How would one verify this?

Thanks for your input.

Tim

Hi Arnis,

Yes, I have saved numerous times as an .MIF; matter of fact for the past couple of days to continue my work I reverted back to using Frame 7.2 and only save the files as .MIFs. I have not had a crash since.

To further complicate matters, I finished creating Book templates in Frame 7.2. and built a book to test the generated lists; page numbering, etc. all functioned correctly. I saved the files (as .MIFs) and moved them onto another system which only has Frame 8 loaded. I opened the files saved them as Frame 8 FM and built a book using the template files. The Frnt Matter section page numbering (lc Roman numerals) changed to Arabic, was not sequential through the different sections regardless of my selections in Format, Document, Numbering in the individual book file/book window.

The table was not imported from Word but created in Frame from scratch. Since I have been having these ongoing problems I wanted to rule out anything external causing the issue(s). I currently have two graphics in the document (TM Block and Logo) both are .jpg. Although, I am switching to PNGs and was not aware of the issue-thanks.

So, I plan to return to using 7.2 and wait until these issues are resolved.

Thanks again for your response.

I have had the same problem (have had over 60 crashes in two weeks) running Frame 8 on Vista and XP systems - both new, stout systems.

The last four crashes happened within 1.5 hours and included the same INternal Error codes:

11/8 6:48 PM
=== Header Begin ===
Internal Error: 8004, 6952719, 4841390, 4841118
FrameMaker 8.0.0 for Intel
Build: 8.0p236
Window System: MSWindows
Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 2)
Generated on: Thursday, November 08, 2007 6:48:23 PM
To file: c:\program files\adobe\framemaker8\FrameLog_07.11.08_18.48.23.txt
=== Header End ===

I was creating new templates and imported some formats from some I had created with FM 5.5/6.0. Adobe mentioned the templates may be corrupt (I've never had a problem before with them), so I created them again from scratch. Did not matter, crashes still occurring.

I noticed several things that may be a symptom or bug(?).

- The Color Definitions seem to expand from the several default definitions to maybe somewhere over 200 (Definitions named RGB XXXXXXXXX). And you cannot delete them.

- Table formats (specifically Double line for table header does not continue on the next page) inconsistently applied.

- Cannot print any Frame or PDF documents - both immediately crash. I can create PDFs from Frame using "Save As."

- Could not revert back to an editable document per instructions after creating a review only document.

I scoured the forums when the problems started occurring and did not find any related info until today - so I am not alone!! I copied the crash logs and sent them to Adobe to reopen the ticket last Friday(?) and have not heard from them.

And I thought I was finally rid of the exacerbation of crashes and corrupt docs replacing Word as our main tool!

No offense taken, but you're kinda misquoting me. What I said was the same thing you said -- if other memory hogs (PS; Illustrator) are running at the same time as FM, then FM ends up without enough RAM, especially if it is also trying to process graphics.

Instability is a whole other issue, but either way the only practical way to compensate is by adding more RAM.

Art

Larry, you mentioned using graphics as being when the crashes seem to occur, and you also mentioned it happening on pasting.

Could you tell us what type of graphic files you're using? What is the source application that you're pasting from? How many graphics do you have in an average FM file?

Also have you experimented with using referenced graphics rather than copied (pasted) in? Several advantages for referenced graphics: 1) makes your FM files much, much smaller, 2) removes significant amounts of re-work when graphics are updated, 3) makes the files more portable, 4) uses much less memory -- some graphics formats expand the FM file size dramatically when pasted into FM, often several times the graphic's actual file size on disk.

I have to say I agree with the other folks that 1gig of RAM is more than likely your culprit; years ago I experienced instabilities in FM that were resolved once I got more RAM.

Thanks Jack - I'm waiting on a response from Adobe Tech Support now...I'm feeling like an "early-adopter" here, which I have always tried to avoid. If I get a response/solution, I'll post it here in case other poor souls are experiencing what I'm going through.

This may not help but I'll throw it out there anyway. I was running FM8 under Vista and had problems when I held down my mouse button too long. FM8 froze and I often lost data. I called Adobe and they asked if I had used AutoPlay when I loaded the app. Told them I had. They suggested uninstalling it and then reinstall through Windows Explorer by opening the CD's Framemaker8 folder, right-clicking on the Setup icon, and selecting Run as Administrator. Supposedly it fixes several problems. It didn't seem to fix mine but it may be worth a try. I did not have to reactivate the software when I did that. Also, did you contact Adobe and provide the error message numbers to them. They were very helpful when I called, as well they should be.